{"id":153,"date":"2019-02-21T12:01:00","date_gmt":"2019-02-21T12:01:00","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/2019\/02\/21\/best-practices-of-ansible-role\/"},"modified":"2021-01-04T22:12:21","modified_gmt":"2021-01-04T16:42:21","slug":"best-practices-of-ansible-role","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2019\/02\/21\/best-practices-of-ansible-role\/","title":{"rendered":"Best Practices of Ansible Role"},"content":{"rendered":"
I have written about Ansible Roles in my career. But when I talk about the \u201cBest Practice of writing an Ansible Role\u201d, half of them were not following the best practices. <\/span><\/div>\r\n
When I started writing this blog, I had only limited knowledge of Ansible Roles and about the practices being followed. But reading more on Ansible roles has helped in enhancing my knowledge.<\/span><\/div>\r\n
Without the proper understanding of the Architecture of Ansible Role, I was incapable of enjoying all the functionality for writing an Ansible Role. Earlier, I used \u201ccommand\u201d and \u201cshell\u201d modules for writing an Ansible Role.<\/span> Here, in this blog, I’ve discussed the best practices of Ansible Role. Let’s <\/span><\/div>\r\n
read these in detail.<\/span><\/div>\r\n
\u00a0<\/div>\r\n

<\/p>\r\n

\u00a0<\/div>\r\n
Advantages of Best Practices<\/b><\/div>\r\n
\u00a0<\/div>\r\n
\r\n