roles are there to make reusable units of non trivial set of tasks, sometimes its just easier to create a simple tasklist and use include:.
If it is becoming 'painful' its a sign of trying to put square peg in round hole. Ansible is designed to be simple, also it is very flexible and can be used in many different ways. It leaves organization up to you but sometimes this becomes an issue, specially if coming from other tools from which you got into the habit of complexity. I recommend taking a step back at this point, go back to you goal and think of simpler approaches. for the original poster, you can use roles == features or even a 'wrapper role' that uses the feature roles as dependencies. I generally equate 'machine roles' == groups and use plays to group 'feature roles'. -- Brian Coca Stultorum infinitus est numerus 0110000101110010011001010110111000100111011101000010000001111001011011110111010100100000011100110110110101100001011100100111010000100001 Pedo mellon a minno -- 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/CADn%2BHsyF_rJST5VOmc4xSUg9As86Ls3iWnhAa2f_t4CEXLGSxw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
