Is there some way to get relative paths in included playbooks to be relative to themselves rather than their parent playbook? This would be useful for lumping the files and templates for a particular play together in a folder with that playbook.
If this isn’t currently possible but would be desirable, I’d be happy to attempt to add this functionality.
Thoughts?
I think this is already the case, because in my case, where I have:
provision.yml
plays/
kickstart-boot.yml
kickstart-facts.yml
kickstart-media.yml
kickstart-post.yml
templates/
kickstart/
ks.cfg
provision.yml
No this isn’t what I see at all, perhaps it’s different for local_action? I’ve been testing it with “copy” and whatever src i specify gets looked for in the parent playbook folder, not the child playbook.
This feature is in plan for 0.9 and it will allow them to be relative to either.
Could the difference be explained by me including complete plays from a master playbook, while some people are using includes to include sets of tasks inside a play ?
Because this definitely works for me as I explained, and we have 40+ plays included in various playbooks (one level up). All plays have everything (local and remote actions) relative to the location of the play.
So you may have to give me an example in order to understand what you're doing.
I will take care of this.
-- Michael
Michael is this something you’d welcome pull requests for? I’d really like this feature and so would be keen to help in some way (I actually already organize my plays in their own folders with their associated files but then get around the problem by using a dirty script to run each play individually in sequence).
I want to take the opportunity to refactor the way plays are dealt
with, and have some rather specific things in mind that I want to
(need to) accomplish.
I'm not clear how that will look yet, so I'd say you probably want to wait.
We do, however, have quite a large queue of other things if you want
to pick something to work on, that would be great!