I'd argue that having a common role would be the approach to take, with follow-on roles having a dependency on the common role. For ease of maintenance, that's the way to go. I don't think in-depth standards for Galaxy roles has been discussed yet, at least not that I've heard (and not on this topic). Since "common" roles to be a standard practice amongst most Ansible users, their use in Galaxy should be appropriate.
On Tue, Feb 11, 2014 at 12:05 PM, James Martin <[email protected]> wrote: > As I noted on an early message -- I'm working on some riak related roles > for galaxy -- a number of the roles do some similar operations -- setting > up some repositories, doing some simple configurations, etc. > > Is it better to contain those common operations in a common role and have > the other roles I'm making depend on it? Or should the roles be fully > self-contained? > > - James > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
