The dependency algorithm still needs optimisation... :-) I suspect that some of the issues are due to added functionality... Some things like the addition of the strategies probably added extra requirements. There is another post where someone else moving from 1.9 to 2.0 now gets an error about circular dependencies so I think that they have probably also increased the dependency checking.
I am not sure I agree with the way that you are using dependencies myself... In my opinion a dependency would be something like some of our servers need perl on them, all of our web servers also need perl on them. Installing perl would be a role, and the web server role which requires perl in order to work would have a dependency. In my site.yml I group servers by OS, and then call different roles for Debian based, RedHat6 and Redhat7. the Redhat6 and Redhat7 roles both depend on a Redhat Common role. Finally All Linux calls a LinuxCommon role. I could call a linux common role instead and have that depend conditionally on Debian, Redhat6 and Redhat7 roles with the last two being dependent on Redhat Common. I might change to just that, particularly as I need to add AIX support. Once the OS is configured using those base roles, individual roles are used to configure application specific things. But they do not have dependencies on the base OS roles. -- 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/19f751d5-0923-4cee-bbe9-c491802c5213%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
