06 Objective: Orchestrated Strikes – Playbooks

Variables – loaded.
Templates – locked.
Tasks – trained.

Ghosts may notice – we’re flying low with plain text variables – for now.

Playbooks – The Orchestration Of The Special Operations

If vars and tasks are the fuel – playbooks are the engine.
They decide. They run. They summarize.

You feed them with:

• Subjects of interest – target hosts or groups.
• Behavioral instructions – how to approach the subjects.
• Roles – the modular pillars of Ansible Ghost Ops.
• Tasks and imports – sometimes you execute in-line. They introduce tactical noise.

- name: Example Ansible Playbook
  hosts: hardened_servers
  ansible_user: ds
  become: true

  roles:
    - harden-kernel
    - harden-fs
    - harden-services

  tasks:
    - name: Example Task In Playbook
      ansible.builtin.debug:
        msg: "Be silent. Be Ghost."

The blade is sharp with surgical precision.
It’s Ghost Ops ready.

ansible-playbook – The Art Of Execution

Ansible strikes with multiple blades.
One of them: ansible-playbook.

Precise. Useful. Deadly.

In doubt ask:

ansible-playbook --help

To strike – enter the playbook directory:

ansible-playbook -i inventory.ini playbook.yaml

The blade swings. Targets hit. The focus is sharp.

Want to narrow the focus?

ansible-playbook -i inventory.ini playbook.yaml --limit hardened_host1,hardened_host2

Precise execution.

Sharpen The Blade – Tactical Command Options

This is not tutorial.
This is survival.
Use man and ansible-playbook --help to see through the fog.

Yet, the Ghost Ops sometimes need tactical adjustments.

• --ask-vault-pass: Prompt for the Ansible Vault password.
• --ask-become-pass: Prompt for the sudo or su password.
• --ask-pass: Prompt for the connection password.
• --check: Simulates execution without making changes.

Don’t overdo.
Don’t overcomplicate.

Focus. Clarity. Signal.
The Operator’s best allies.