Ansible Tutorial Class 9 | Ansible Tags Examples | Tech Arkit

Ansible tags are used in larger playbooks to execute the playbook with tags so that only specified playbooks will execute out of the playbook tasks, Even after running entire playbook.

#ansible #tags #automation

Ansible Automation Playlist:
RHCSA - Red Hat Certified System Administrator PlayList:

Follow Us on Social Media

Post your topic, we will make videos for you

Ansible Course
Automation with Ansible Course

Ansible Lab Setup

Ansible Inventory configuration

Ansible Ad-Hoc Commands with examples

Writing your first Ansible playbook guide

How to variables in Ansible playbook

Conditionals and Loops of Ansible playbooks

Ansible playbook challenge

Deploy LAMP Stack Using Ansible Playbook

[danielyount]

Good overview of the capability of Ansible playbooks. I'd known Puppet, but its written in Ruby and uses other Ruby deps. Making it harder to maintain, while Ansible is written in Python, which most distros install as a base anyway, since they use it for their utilities. So now learning it, will see how that goes and its pros and cons.

[ashoksmg]

Thank you sir, I really appreciate your effort to make videos on Ansible, I hope I will learn complete Ansible with you only, thanks

[IndiasHeart]

You could also add(--skip-tags) which is very useful

[thiyagutvse]

If I run copy how it's run because two copy tags are available

[Oswee]

Typically you do not place tasks in the playbooks. It's antipattern. You have roles and tasks and handlers for that. Variables shoud be moved in some of variables files. MySQL should be installed as separate role and Apache as separate role. Then you just import them booth in single playbook called "lamp.yml" if you wish. Also single line modules contradicts the documentation and is antipattern. It simply reduces readability and increases maintanance cost. Please do not teach bad practices even in simple examples.