I just want to confirm that there is no way to include playbook from a role different than current one without resorting to absolute paths. I want this:
- roles/
- app-core/
- tasks/
main.yml
permissions.yml - app2-core/
- tasks/
main.yml
And in roles/app2-core/tasks/main.yml have this one to work:
- include: roles/app-core/tasks/permissions.yml
This doesn’t work currently. Moving permissions to a separate role looks ugly, because setting permissions is a just common task - not a role - and I’d like to avoid code duplication. It looks like any role playbooks except main.yml are pretty useless, because what is the point in splitting main.yml to parts if the code can not be reused anywhere else?