On 7 May 2014 13:08, Rohan Nicholls <[email protected]> wrote:
> - Just calling a silo role by name would no longer work, and specific > paths would have to be given, so a bunch of the nice out of the box > convention over configuration would break. With this structure, your role name really is e.g. "silo/create", which I use myself often, I don't see any downsides to that. Also, if update and create are very similar, only differing by a couple of tasks, you could consider using conditionals on a role parameter, e.g. when: function == update? Serge -- 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/CAEhzMJBBP5g84DaZU_gQtJOT5vFb_o7YHLgC8sy_jHizdbguNw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
