# Playbook interdependencies

**URL:** <https://forum.ansible.com/t/playbook-interdependencies/13602>\
**Category:** Ansible Project\
**Created:** [October 3, 2013, 3:14pm UTC](https://forum.ansible.com/t/playbook-interdependencies/13602 "2013-10-03T15:14:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jim\_Van\_Fleet](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@Jim\_Van\_Fleet](https://forum.ansible.com/u/Jim_Van_Fleet)\
**Post date:** [October 3, 2013, 3:14pm UTC](https://forum.ansible.com/t/playbook-interdependencies/13602/1 "2013-10-03T15:14:24Z")

</div>

I am preparing a playbook to configure my use of [papertrailapp.com](http://papertrailapp.com).

In turn, producing a file like [https://github.com/papertrail/remote\_syslog/blob/master/examples/log\_files.yml.example](https://github.com/papertrail/remote_syslog/blob/master/examples/log_files.yml.example) is desired.

For my use case, I cannot rely on a single kind of web server or database being in place. I can rely on having used a playbook from roles/ to have been referenced/run/included, whatever the appropriate term is.

I’d like the entries to be determined by the other playbooks that run along with it. For example, when I include the torquebox role, the log\_files.yml should include /var/log/torquebox/\*.conf, but that won’t be present unless the role has run alongside/before the papertrailapp role.

Is this a sensible thing to desire? Is there a supported way to do this with ansible? I can understand how to store desired log file locations inside each role’s vars file, but then how would I aggregate them into the file in that way?

Thanks so much for ansible, I’m a big fan.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [October 3, 2013, 7:54pm UTC](https://forum.ansible.com/t/playbook-interdependencies/13602/2 "2013-10-03T19:54:43Z")

</div>

I am having a little bit of a hard time understanding what you are trying to convey. This is probably on my end.

1.3 features role dependencies, which are perhaps quite relevant, and are documented in the roles sections.

I’m about to push out a nice docs reorg that makes all this easier to find, but it’s there now in the playbooks chapter if you want to take a look.