This behavior is expected. The variables defined in Role A should be scoped for A unless defined within your inventory or any of the other places outside the role that variables are defined.
If variables from a role were implicitly available broadly through their declaration, you can have nasty side effects and potential security problems. Recommend looking at https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html for more info. Sent from my iPhone > On Jul 11, 2019, at 2:47 AM, Shashank Dutt Jha <[email protected]> wrote: > > I have defined a role : say A > another role B which includes role A > > in role B when I try to use variables defined in A, I get var undefined error. > > I tried using public: yes when including role A. Still same issue. > > This is correct behaviour? > > Or I should be able to use variables defined in a role in my tasks/ role > tasks after including it? > -- > 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/705f9907-6f37-49f6-9372-aad55d12fc4c%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/20C3BCFB-D196-419A-88BC-B200AC1DA595%40gmail.com. For more options, visit https://groups.google.com/d/optout.
