Targeting a Single Host in Ansible Playbooks

When managing user tasks across multiple machines with Ansible, you might find yourself needing to run playbooks on a specific host. By default, playbooks can be set to target all hosts, which can lead to unintended consequences if not handled carefully. Here’s how to effectively limit playbook execution to a single machine.

Inventory Setup

First, ensure your inventory file is organized. For example, you can create a simple inventory file like this:

# file: hosts
[office]
imac-1.local
imac-2.local
imac-3.local

Running Playbooks with Limitations

While you can use the --limit flag to specify a single host when executing a playbook, this approach can be risky if you forget to include it. Instead, consider defining the target host directly within your playbook.

Example Playbook

Here’s an example of how to structure your playbook to accept a target host as a variable:

# file: user.yml
---
- hosts: '{{ target }}'
  tasks:
    - name: Manage user
      user:
        name: example_user
        state: present

Executing the Playbook

You can then run the playbook by passing the target host as an extra variable:

ansible-playbook user.yml --extra-vars "target=imac-2.local"

This method ensures that if the target variable is not defined, the playbook will not execute any tasks, preventing accidental changes across all hosts.

Additional Safeguards

To further enhance safety, consider implementing checks within your playbook to validate the environment before making changes. This can include verifying the current state of the system or using Ansible's run_once directive for tasks that should only execute on a single host.

By following these practices, you can effectively manage user tasks in Ansible while minimizing the risk of unintended consequences.