On Thursday, May 29, 2014 1:52:16 AM UTC-7, Paul Oyston wrote: > > Just to confirm, I wasn't suggesting any form of inheritance in any way,... > I understand what you are saying, but unless the role that you run first (avoiding the d word) knows to expect a template from the later role then you have an issue. If all roles were written to add fragments and assemble configuration files then they could work together (or for applications that have configuration directories that's already solved for you). But then you are either going to have to go in and retrofit all existing roles or only work with a subset. There is no enforced coding standard for roles so I think that we are going to have to live with the current situation.
If you write your roles to be accepting of fragments then that's the best that you can do... Adam -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/96a255ec-5750-4fcf-a7f1-2f6fba165c73%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
