If they're common to all of the roles you're writing, best to make the common part a role of its own and use the dependency system we have in place. Just be sure that when you're listing the deps, that you do so in the "username.rolename" format so that galaxy will properly link them as dependencies when downloaded with the ansible-galaxy command line tool.
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.
