> Even though they are sub directories to A & B, don't
> inherit anything (as in, they don't get vars from the parent role
> because there's no such thing). They are fully separate roles.
not nitpicking, but out of curiosity - why then when I first call B role
var gets substituted for B/install ? If what you're saying is correct my
experience suggests it's an inconsistent behavior at the moment. Which is
to say - I did not find information so far that would've helped me to
predict such an outcome.
Tell me what you expect the output to be, and we can work to figure
> out how to make it so.
>
>
in that particular case I was testing the waters to see whether "nested"
roles would work and I can set common vars for "B/{install,configure}"
instead of populating them either in both places or making a tighter fit
between groups and roles (which we know are not always 1:1 match). From
that little sample I see that the only way for me to set things up for both
B/install and B/configure is to either make a design decision to keep
group->role a 1:1 map (well more like 1:n but what's important we can't
have same role applied to two different groups under those conditions).
In other words I was looking at nested roles more like OOP concept - to get
common attributes I introduce common parent, but it's not the case here.
Let me go back and review my design ideas and see whether I can find a
different way of expressing what I need.
Thanks for bearing with me here as I'm trying to sort things out.
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
