-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Fix include_role with loop #92
Conversation
b607512
to
6eed68c
Compare
6eed68c
to
6ca3cf5
Compare
6ca3cf5
to
80cce74
Compare
e91b21d
to
17e43b7
Compare
Hi @haidaraM My impression is that the changes would display a warning, but still continue running what it possibly can parse? I'm still seeing crashes after trying this code:
I can create a new issue if you'd prefer tracking this separately, just lmk. |
Can you provide me a minimal version of your playbook that is failing or run with No need to create a new issue. I will reopen the old one :-) |
It displays a warning and moves on to the next task but in your case, I have missed something. |
To create a minimal reproducible version of my playbook I reverse engineered to understand what task is failing,
I tried to replicate the include-pasta I've created a simple role that tries to trigger the same issue but that runs as intended. The source is too complex and containing secrets that I do not wish to share. Will continue trying to replicate it minimally but I got no further ideas so leaving this here for now. |
Ok. Can you try the version on this PR #99 ? |
Certainly, one moment. |
Should fix #80