I agree, I'm going to move them into the roles, especially since the slack role doesn't really accomplish much.
With that being said, say the dependent role was a bunch of API calls to accomplish some task. In this case, I could call include role and call for a particular task within that role. If I added it as a dependency to my calling role, I would end up in the same position. Am I just using Ansible and roles, the wrong way here? How can you add a role as a dependency without it being called by default? Seems like that isn't possible. Any alternative approaches? Thanks for your response :) On Jul 7, 2017 4:22 PM, "Dick Davies" <[email protected]> wrote: It doesn't sound like you want a dependency at all. Why not just stick the slack tasks in the relevant roles? You're losing a lot of clarity trying to use a role to save a bit of typing, and from the look of that gist you aren't even saving much typing :) On 7 July 2017 at 20:08, Lee Connell <[email protected]> wrote: > Hi all, > > I have a role that has a dependency on another role, however by default, > Ansible will execute the dependency first. In my case, I do not want this to > happen. I don't want the role executed automatically at all. The role that > is requiring this dependency will call it on its own within it's own tasks. > Right now, I am checking if a variable is defined, and if it is, then the > tasks within the dependent role will run, but you still see the task line > item in the playbook output. I would like to avoid it attempting to execute > it altogether. > > https://gist.github.com/lconnell/dfb1dc5383517b3bdd9c4832ae9027e2 > > > -- > 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/82198539-1af4-4885-8254- ae9788b9d85b%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/ansible-project/A_-BJFtygS8/unsubscribe. To unsubscribe from this group and all its topics, 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/CAK5eLPTNcibS6t92e1rEm%3DYiAqV6GvfYU0h66fDrw4tehT0NFQ %40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- 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/CA%2BHjMCJ4FUAfrnm-zgPc3jTg1%2BSfpG4JtR9dwxPszfChDmVJEA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
