@Christian, those are my thoughts for the future of the service module, this package module will serve as a template on how to split it and keep backwards compatibility using the generic module as a placeholder. Just need to add service system detection to facts and then use those internally.
As for keeping the policy in a single place, the same can be achieved by just making the ssl cipher string into a common variable and then have each template reference it. This does not work for all cases but I find it better to keep specific tasks for each OS and then abstract the common data, than the reverse which abstracts the common task but requires abstracting the non-common data. Again, I'm all for choice, in this case I think it is an illusion as you update 1 common yaml file and 2 non-common yaml files vs 2 common yaml files and 1 non-common yaml file. -- Brian Coca -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJ5XC8khiXdzztKqyb6zgX47%3DjyJT77t%2BOM-vnMy%3DCjRkhYWGg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
