On 22. nov. 2016 20:25, [email protected] wrote: > Ok so I ended up rolling back to playbooks in the top level directory. > > I got myself turned around a bit here. The {{roles_path}} as part of the > include actually wasn't working; which, I should have known since you can't > use ansible.cfg parameters in tasks like that. I think my main problem is > that I'm using 'include' statements to include roles during plays. In this > way, I function them out as reusable functions for different roles. I was > warned that this is a nonstandard, in favor of meta dependencies. I think > that's coming back to bite me now. > > Sample: > - name: database param_def select > # Initial select statement to see if db changes are required > tags: db > include: roles/role_utility_sqlplus/tasks/main.yml > vars: > query_type: "select" > table: "param_def" > filename: "dbselect_paramdef_mhe.sql"
You could use include: ../roles/role_utility_sqlplus/tasks/main.yml Or you could set roles_path to a absolute path instead, but then the problem is that every Ansible users need to have the files in the same path and thats unpractical. -- Kai Stian Olstad -- 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/d518441c-4c06-d0bc-a636-b497d3f82f3b%40olstad.com. For more options, visit https://groups.google.com/d/optout.
