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
Run Ansible Playbook Grapher against Meza #63
Comments
Errors with
Even though
and
After upgrading pip (still in the venv) I was able to install ansible playbook grapher
|
From the config directory, I get an error because we use an old module that can't be determined. [config]#
|
I tried to work through the errors with the following, but still ended up deactivating the venv because the create command accidentally used system python instead of python3.11 which is erroneously??? reported by ansible --version in the VSCode terminal
|
In this Virtual Environment, it shows Python 3.11 being used and maybe Ansible Core 2.16.3
|
This should be refined so that
BUT The site diagram shows just how big and monolithic the system is. The real action item is to make the whole system much more modular and composable so that it's not a directed graph of 742 nodes. |
https://github.com/haidaraM/ansible-playbook-grapher
Run this and output either Graphiz png or possibly Mermaid charts that we can put on-wiki.
The text was updated successfully, but these errors were encountered: