AnsiblePilot — Master Ansible Automation

AnsiblePilot is the leading resource for learning Ansible automation, DevOps, and infrastructure as code. Browse over 1,400 tutorials covering Ansible modules, playbooks, roles, collections, and real-world examples. Whether you are a beginner or an experienced engineer, our step-by-step guides help you automate Linux, Windows, cloud, containers, and network infrastructure.

Popular Topics

About Luca Berton

Luca Berton is an Ansible automation expert, author of 8 Ansible books published by Apress and Leanpub including "Ansible for VMware by Examples" and "Ansible for Kubernetes by Example", and creator of the Ansible Pilot YouTube channel. He shares practical automation knowledge through tutorials, books, and video courses to help IT professionals and DevOps engineers master infrastructure automation.

Ansible Tags: Run Only Specific Tasks in a Playbook (Guide) — Video Tutorial

How to run only one task or specific tasks in an Ansible playbook using tags. Use --tags, --skip-tags, always/never tags.

Watch on YouTube · Read the written article

Ansible Tags: Run Only Specific Tasks in a Playbook (Guide) — Video Tutorial

How to run only one task or specific tasks in an Ansible playbook using tags. Use --tags, --skip-tags, always/never tags.

Watch Video

Watch "Ansible Tags: Run Only Specific Tasks in a Playbook (Guide)" on YouTube

What You'll Learn

Full Tutorial Content

How to run only one task in an Ansible Playbook? I'm going to show you a live Playbook with some simple Ansible code. I'm Luca Berton and welcome to today's episode of Ansible Pilot. How use tags statement in Ansible Playbook? - `--tags all` - `--tags tag1` - `--tags [tag1, tag2]` - `--skip-tags [tag3, tag4]` - `--tags tagged` - `--tags untagged` Today we're talking about Ansible tags statement. When your Ansible Playbook starts to grow up it's useful to define tags to allow a more granular execution. You could define one or multiple tags at the individual task, include, import, play, block, role level. Tags also could have tag inheritance properties. The easiest way to run only one task in Ansible Playbook is using the tags statement parameter of the "ansible-playbook" command. The default behavior is to execute all the tags in your Playbook with `--tags all`. You could specify to execute a single tag with `--tags tag1` or a list of tags `--tags [tag1, tag2]` You could specify also and use the negate logic to exclude some tags`--skip-tags [tag3, tag4]`. Another convenient way is to execute only the code with tag `--tags tagged` or without `--tags untagged`. Links - [Tags](https://docs.ansible.com/ansible/latest/user_guide/playbooks_tags.html) ## Playbook How to run only one task in Ansible Playbook? I'm going to show you one simple Ansible Playbook with two tasks and two tags and how to select one or another via the command line. code ```yaml --- - name: tags Playbook hosts: all gather_facts: false tasks: - name: example 1 ansible.builtin.debug: msg: "example 1" tags: tag1 - name: example 2 ansible.builtin.debug: msg: "example 2" tags: tag2 ``` execution default ```bash $ ansible-playbook -i virtualmachines/demo/inventory variables/tags.yml PLAY [tags Playbook] ********************************************************************************** TASK [example 1] ********************************************************************************** ok: [demo.example.com] => { "msg": "example 1" } TASK [example 2] ********************************************************************************** ok: [demo.example.com] => { "msg": "example 2" } PLAY RECAP **************************************************************************************** demo.example.com : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 ``` execution tags tag1 ```bash $ ansible-playbook -i virtualmachines/demo/inventory --tags=tag1 variables/tags.yml PLAY [tags Playbook] ********************************************************************************** TASK [example 1] ********************************************************************************** ok: [demo.example.com] => { "msg": "example 1" } PLAY RECAP **************************************************************************************** demo.example.com : ok=1 changed=0 unreachable

About This Tutorial

Read the full written article: Ansible Tags: Run Only Specific Tasks in a Playbook (Guide)

Topics Covered

Related Video Tutorials