Could you say what tool you are using to generate puml files? Is that tool is FOSS kind of tool or your internal tool? I was looking for a tool online but the one I found was rather old and not working correctly.
As far as I know we have a combination of python scripts that generate PUML model text from the schemas in the YAML/OAS files. A FOSS is then used to create the diagrams from the PUML text.
Would be best for our generation wizard @Knut Johannessen to describe the process.
In the (medium/far?) future, there's hopefully going to be an ongoing import from the Open API model assets into TMF's MODA repository, which is their new central place for holding all models.
PUML generates images (both SVG and PNG) that have the diagram code embedded as metadata.
If TMF could provide these PUML PNG/SVG files in the TMF WIKI (within the API project), then TMF members could extract the code and modify it. This would allow us to generate our own diagrams, including our own API extensions.
The tooling we use to generate the diagrams for the API user guides can be found here: https://github.com/knutaa/oas2puml/packages/781389.
The latest version is 6.6.8 with this executable jar file: apidiagram-6.6.8-20230829.193646-1-exec.jar.
Run with a command like
java -jar apidiagram-6.6.8-20230829.193646-1-exec.jar diagrams --openapi <oas_file>
Some help on command line arguments can found as
java -jar apidiagram-6.6.8-20230829.193646-1-exec.jar --help
Arguments that may be relevant:
--target-directory - for the generated output files
--generate-images - to also generate png images based on the embedded plantuml version
--config - used to modify the embedded (internal) configuration used by the diagram generator
--keep-inheritance-decorations - decorations are added like shown for Organization
As seen in the user guides, the diagram generator tries to split large diagrams into "sensible" fragments without user input. There are ways to modify that behavior when necessary.