AAP and galaxy roles best practices

Get Help
, , ,
1

I am migrating my config management stack from puppet/hiera/foreman to AAP. I am getting the hang of it, but I am confused about how I should be using galaxy roles. I am using AAP 4.5.13, and RHEL satellite for my inventory

For instance:
I have a bunch of hosted servers. Some need databases, some need nginx, some need apache, etc… I would like to use group, and host_vars so that I don’t have dozens of playbooks laying around. So far, I have not been able to get the AAP template run to pick up the host_vars… Just don’t want to paint myself into a corner…

Sample playbook:

  • hosts: all(limited in the AAP template)
    gather_facts: true
    become: true
    vars_files:

    • roles/linux_server/vars/encrypted_vars.yml

    roles:

    • role: linux_server
    • role: dns_server
    • role: bertvv.bind

The bertvv.bind role is listed in requirements.yml and that seems to work fine. The “dns_server” role is something I initialized, and put all of the bertvv.bind variables in a group_vars yaml that matches the name of the foreman group from satellite.

Sorry for the ignorance, but I am not finding much out there. I also may not be using the correct terminology!

thanks in advance.