Feature request: Verbose output/debug info option

[Michael T. DeGuzis]

Could we add a debug / verbose option so we know the command is doing things in the background? Is the command hiding all the output from cdk synth?

npx cdk-dia --tree cdk.out/tree.json --target diagram.png 

Unfortunately, the stack I am working with has 2 million (yes 2 million) lines in tree.json

[Tom Roshko]

HI @mdeguzis ,

Wow, 2 million lines!

cdk-dia doesn't hide cdk synth, it doesn't even use it. It assumes / requests you did it ran it before and therefore the tree.json exists.

Generally, it has four main steps: import tree -> generate diagram (an internal representation) -> render to a .dot file -> execute Graphviz in the .dot file.

I am happy to add a -v flag that will report these steps so we can get an idea of what is taking so long.

Meanwhile, you might want to inspect whether a diagram.dot has bee generated. That would indicate where is the process stuck. My wild guess is that Graphviz is taking long. You might want to consider using the --include flag to generate sub diagrams.

[Michael T. DeGuzis]

Yes :)

$ wc -l build/cdk.out/tree.json 
2,351,246 build/cdk.out/tree.json

Meanwhile, you might want to inspect whether a diagram.dot has bee generated
Where is diagram.dot? You mean diagram.png? Or a similar file in my output directory?

[Tom Roshko]

it should be in you cdk app work directory. in the same one where diagram.png is created on a success run

[Michael T. DeGuzis]

I let it go for a while and it does complete. It's very interesting, as the PNG is extremely horizontal and the more I zoom, the more pixelated it is:

I'll have to look into the sub diagrams you mentioned.