Red Hat Certified Engineer (RHCE) Ansible Automation Study Guide

Chapter 7. Ansible Roles and Collections

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 8th chapter of the final book. Please note that the GitHub repo will be made active later on.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

You have seen how to write playbooks to execute specific tasks throughout the book. For example, we have covered tasks such as copying files into managed servers, creating users, manipulating files, or installing packages (such as the Java Virtual Machine).

But, what happens when you need to reuse the same tasks through different projects?

Do you remember one of the first examples in the book, where we reviewed a complete playbook for deploying a Java service?

The steps included in the playbook covered:

• Installing dependencies (JVM) on managed hosts.

• Creating required directories.

• Copying and configuring the application on managed hosts.

• Configure supervisor.d to control the application.

As you can imagine, this process can be repeated for any Java project. How can you share this playbook among other projects so they don’t need to repeat the development of the same playbook over ...