cfn-diagram VS cdk-dia

What do you think, is it worth writing a patch for cfn-diagrams to create these links automatically?

{ "week": [ { "Id": "16", "AWS-Services": [ "AWS CloudFormation", "AWS CloudTrail", "AWS Config", "Amazon CloudFront", "AWS Cost Explorer", "AWS Lambda", "AWS Key Management Service", "Amazon Athena" ], "Languages": [ "Python", "nodejs", ], "Tools": [ { "name": "ORGTOOL", "github": "https://github.com/daknhh/aws-orgtool" }, { "name": "cfn-python-lint", "github": "https://github.com/aws-cloudformation/cfn-python-lint" }, { "name": "cfn-diagram", "github": "https://github.com/mhlabs/cfn-diagram" }, { "name": "Taskfile", "github": "https://github.com/Wildhoney/Taskfile" } ], } ] }

cfn-diagram how many times have you wished you could take your CloudFormation YAML or JSON and then visualise it? When this open source tool provides a CLI as well as integration into tools like VSCode that help visualise CloudFormation templates as draw.io diagrams. Very nice Lars Jacobsson and the MatHem tech team. There is also the experimental cfn-diagram-ci which you can have a look at as well.

Why use this over just generating the diagram when it's done: https://github.com/pistazie/cdk-dia

I want to auto-generate diagrams for my infrastructure as part of my CI/CD pipelines, that updates documentation. I recently stumbled upon cdk-dia, a very nice tool that does exactly what I want, except it is geared towards stacks written in typescript - then it becomes possible to customize the diagram (hiding or showing details) in code, via decorators.

It's just as easy to write your architecture in code, then generate the diagrams. If you use CDK, cdk-dia can be handy.

And then there are projects like CDK-Dia that are taking infra documentation one step further.

https://github.com/pistazie/cdk-dia