Chris, thanks; so then using task-less roles doesn't look so bad... I'll give a try to both approaches and see. Thanks again! -Y.
On Thursday, December 31, 2015 at 6:52:57 PM UTC+2, chris meyers wrote: > > The task-less role is good because you can capture the dependency fully in > the role (via meta/main.yml dependencies) without depending on some > externally defined data. Further, your data would follow your roles if you > want to use those roles in another project. > > The group_vars/all could also work well in your design IF your roles that > depend on those "shared variables" are designed such that they either (1) > fail when those variables aren't defined or (2) you assign sane defaults in > the role for the "shared variables". (1) is a common problem for me so I > created a required-vars <https://galaxy.ansible.com/detail#/role/6324> > role that i reference in meta/main.yml dependencies to ensure per-role > variables are defined and/or assigned. > > -- 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/640c8551-d9a7-42fc-9228-335c51f8ba1e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
