We started to use (and gradually convert old diagrams to use it) Diagrams as our tool of choice to generate diagrams. The diagrams are generated from Python code and can be automatically updated when the code changes. The diagrams are generated using pre-commit hooks (See static checks below) but they can also be generated manually by running the corresponding Python code.
To run the code you need to install the dependencies in the virtualenv you use to run it: * pip install diagrams rich. You need to have graphviz installed in your system (brew install graphviz on macOS for example).
The source code of the diagrams are next to the generated diagram, the difference is that the source code has .py extension and the generated diagram has .png extension. The pre-commit hook generate-airflow-diagrams will look for diagram_*.py files in the docs subdirectories to find them and runs them when the sources changed and the diagrams are not up to date (the pre-commit will automatically generate an .md5sum hash of the sources and store it next to the diagram file).
In order to generate the diagram manually you can run the following command:
python <path-to-diagram-file>.pyYou can also generate all diagrams by:
pre-commit run generate-airflow-diagramsor with Breeze:
breeze static-checks --type generate-airflow-diagrams --all-filesWhen you iterate over a diagram, you can also setup a "save" action in your IDE to run the python file automatically when you save the diagram file.
Once you've done iteration and you are happy with the diagram, you can commit the diagram, the source code and the .md5sum file. The pre-commit hook will then not run the diagram generation until the source code for it changes.
You can now see an overview of the whole contribution workflow