Is there a technical reason for this? I've only been using Ansible for a few months, but from what I can gather the project has evolved to the point where roles and tasks and includes can pretty much do all the same things - they're all invoked with either [name of role / task / include file.yml] and a bunch of 'key=value' arguments, so it seems like it'd be cool if there was a unified way of invoking them. Perhaps something like:
'action: mysql-server foo=bar' and then leave it to Ansible to figure out where to look for 'mysql-server' (either in library/ roles/ or mysql-server.yml). These 'actions' could just be listed in the order they have to be executed, then you wouldn't need pre-tasks, roles and post-tasks, or seemingly arbitrary restrictions such as 'you can call a task from a role but not a role from within another role, or you can - but only before any tasks from that role' - it'd just be one unified concept. On Friday, 7 November 2014 14:19:02 UTC, Michael DeHaan wrote: > > There will not be a task that applies roles, the "role" directive is for > this. > -- 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/7ceb2b62-fb72-43e2-8dcd-a693b8edcfa0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
