Hi, I wanted to ask same question. Seems that Ansible needs support of some sort of task grouping or name-spacing. Version 2.1 already has over 500 tasks in the single namespace, which affects readability of existing scripts/playbooks - short task names are obscure and long names do not follow common pattern. In my opinion it can become a huge usability problem when number of tasks will grow over 1k (which I believe can happen this year). Having some structure like in documentation http://docs.ansible.com/ansible/modules_by_category.html would already be a big help.
On Wednesday, April 20, 2016 at 10:21:22 PM UTC+3, Azer Huseyin wrote: > > Hi , > > I am investigating ansible to automate our system configuration/management > tasks currently performed using mostly shell scripts. We mostly definitely > will have to write custom modules, but I noticed that ansible doesn't have > module hierarchy. Is there a way to group related modules under "umbrella" > name in OOP style ? > > Using core file module as example, instead of single "file" module with > "state" parameter, having modules "file.copy", "file.link", "file.rename" > etc. > > Thanks! > > BR/Azer > -- 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/f20a2bbd-1f05-44cd-aaf2-8c1062ff72c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
