You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like the diagrams that this tool generates, however the diagram is cluttered by the rather long logical resource IDs generated by CDK.
E.g. in my CDK code, my resource is called search-handler, but in the cloudformation the logical ID becomes searchhandler7b2049725, which is then shown on the generated diagram, which hinders readability. If cfn-diagram could recognise that it's running against a CDK stack and pull the CDK resource names instead of the generated cloudformation names, that would make the output useable for me.
It's not immediately obvious to me how this could be done though. It looks like cdk.out/manifest.json contains some kind of mapping between CDK construct IDs and cfn logical resource IDs, but I don't know if that file covers all resources.
The text was updated successfully, but these errors were encountered:
I like the diagrams that this tool generates, however the diagram is cluttered by the rather long logical resource IDs generated by CDK.
E.g. in my CDK code, my resource is called
search-handler
, but in the cloudformation the logical ID becomessearchhandler7b2049725
, which is then shown on the generated diagram, which hinders readability. If cfn-diagram could recognise that it's running against a CDK stack and pull the CDK resource names instead of the generated cloudformation names, that would make the output useable for me.It's not immediately obvious to me how this could be done though. It looks like
cdk.out/manifest.json
contains some kind of mapping between CDK construct IDs and cfn logical resource IDs, but I don't know if that file covers all resources.The text was updated successfully, but these errors were encountered: