-
Notifications
You must be signed in to change notification settings - Fork 53
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
Do not follow path #16
Comments
Hey, happy to see that you taken this bug :). I just try it, it's work for the first case, but have the same problem for import_playbook. My folder structure :
My playbook follow this workflow : I get the same error :
It try to find |
Hey @mysiki Trying to implement this but as you may know I'm facing a weird issue on ansible <2.7.0 |
hey, just test it, it's ok for the path following but I get another error. I will test it in 2.7 asap |
Same in 2.7.
The tool search : This action is running by a import playbook present in "sub", so private_playbook_dir is set to sub-playbook path.
I maybe need to give you more information ? |
Looks like a variable interpolation issue. Can you test with my latest changes ? |
I have no more interpolation :p
|
Hmm, what is the whole stack trace ? Would like to which line is causing the error. I'm trying to reproduce it locally, can you show me the related lines of the files used ? |
Trace :
It's possible to active/add "debug" mode ? The stack trace are really small, if you can (temporary) add the current file parsing, it will be more easy to debug it. How the tools work, it use --check mode of ansible (because I'm not sure that all my playbook reply correctly to --check :p ) |
I will definitely add some traces to be able to debug more easily :-) Pushed some changes last night, can you check (again) ? The grapher works by using the same classes Ansible uses internally to parse the entire playbook but as I have discovered now, the parsing is scattered between multiple functions/classes. Need to figure out which ones are necessary to get all the information I need to make a graph. |
near ! :D I got this trace :
If I grep file (read it from bottom to top) :
So, manage-infrastructure.yml: import_playbook: servers/manage-servers.yml --> manage-servers.yml: include_tasks: "tasks/manage-cinder-disk.yml" --> manage-cinder-disk.yml: name: role-openstack-cinder-volume --> _create_volume.yml: include_tasks: __manage_volume.yml It seem that the include in role do not start from her path ('./') but form calling playbook_dir |
Can you pull my latest changes, an run it with the option |
hey, it's really good ! I have some warning but I think it's normal like : But I have my svg (I canno't check if all the step are correctly present right now, but it seem to be ok) Test make in ansible 2.7 without -vv |
Cool :-). Will make a release in the next few days |
hello,
I just try this tool but I have some issue on path file.
I have the following file mapping (for sample I have deleted some folder):
When I run :
ansible-playbook-grapher 000-initialize-afs.yml
I get this error :
Of course, /home/ubuntu/AFS/142/playbook-athena-foundation-service-core-infrastructure/loop_tasks/_galaxy_resolve_role.yml do not exist. I have this mapping
If I summarize : 000-initialize-afs.yml call tasks/include_galaxy.yml call loop_tasks/_galaxy_resolve_role.yml
The text was updated successfully, but these errors were encountered: