Mermaid VS terraformer

Mermaid JS is a tool that lets you create diagrams and charts such as flowcharts, sequence diagrams, Gantt charts using simple text commands. It works by converting your text commands into a graphical representation that you can customize and share. https://mermaid.live/

I'm not OP, but I just ask GPT to turn code or process or whatever else into a mermaid diagram. Most of the time I don't even need to few-shot prompt it with examples. Then you dump the resulting text into something like https://mermaid.live/ and voilà.

I like excalidraw for live discussions but if I want to make more detailed or better looking diagrams, I really enjoy these two tools:

- For drag-and-drop/WYSIWYG, I really like DrawIO. They have a web version https://app.diagrams.net/ but I strongly recommend the desktop version https://github.com/jgraph/drawio-desktop/releases/

- For text-as-diagram, I think Mermaid wins this by default since GitHub added markdown support for these: https://mermaid.live/ (This was github's announcement https://github.blog/2022-02-14-include-diagrams-markdown-fil... )

After hours without being able to solve this problem, I decided to make the chart directly in Mermaid's live editor and export it to PNG and SVG. The big problem is that the letters are still too small, the quality of the PNG is very low, and the SVG only works on the web, not with other applications like PowerPoint and Inkscape.

You can export to PNG and other formats in the Mermaid editor https://mermaid.live/

Copy paste code here: https://mermaid.live

‍Terraformer is a CLI tool developed by Google that generates Terraform files from existing infrastructure (reverse Terraform), simplifying the process of adopting Terraform in existing environments and speeding up the initial setup process. Terraformer supports multiple cloud providers, including AWS, Google Cloud, Azure, and others.

Looking into efficient ways to import existing infrastructure. Using Terraformer to get the everything into Terraform and then refactoring into modules, for_each, etc. using moved blocks seems like it would be a good approach. Refactoring them to use existing modules from providers will take a little work and likely going back and forth with terraform plan, and assuming many things won't translate straight across because of what resources a module might be creating and how they are creating them.

We had thought about the ability to convert HCL to Go, but not much thought in querying existing infra to generate HCL (like terraformer). If you want to experiment building on top of Lingon then please go ahead! I’d be happy to help provide the context from Lingon.

If "ClickOps" is your starting point, as you mention, you could try creating a new scratch cloud provider account, do all your "ClickOps", then use a TF export tool (e.g., Terraformer) to see the exported TF resources to find all the references to other TF resources in the cloud resource dependency chain.

I haven't worked with any of the ones that purport to work with AWS, but a quick Google shows terraformer and Terracognita as options - maybe look into trying those out?

This maybe a bit more complicated if you're not into coding/terraform but I'd use terraformer to convert all of your infrastructure from implementation to code while in AWS, then switch providers and with a bit of jiggly of the code implement your infra into gcs as IaC and keep it that way if/when you switch again.

Maybe terraformer could help. I never tried it personally . https://github.com/GoogleCloudPlatform/terraformer

I've been wondering if this tool is any good. https://github.com/GoogleCloudPlatform/terraformer/blob/master/docs/aws.md

If you've to write the code (I assumed you just needed to reorganize it without TG) maybe consider https://github.com/GoogleCloudPlatform/terraformer