Many automation or playbook journeys begin with GitHub, Jenkins, or similar pipelines that are triggered manually or by an event. This approach works for most scenarios but has some limitations.

Git vs Config Focus

CI pipelines are built around Git repositories, branches, and commits, with limited environment support. Mission Control playbooks focus on configuration items and health. With a pipeline, you select a Git commit and environment to execute.

With a Mission Control playbook, you select a configuration item to operate on and trigger events (e.g., config changes, health issues, timeouts). This approach offers several advantages:

• Discoverable: When viewing the cluster, VM, or pod, you can instantly see which playbooks are available. With CI/CD-based playbooks, you must know which pipelines to call and what parameters to use.
• Secure: Pipeline permissions are based on files and environments. Playbook permissions are based on actions and attributes of the config item (e.g., application owners can restart or scale their applications only).