Among all the ways to represent infrastructure, code, config, SQL etc I always wonder why visualization or no-code isnt preferred. To me infra is complex enough yet has lots of interdepencies that are very well represented visually like a system design diagram. Unlike code, there isn't much conditional logic. There's a lot of edges cases and state manipulation which can also be represented visually. I'm hoping your SQL approach also paves some way as SQL is nothing but tabular visualization in that sense.
By "cloud infra" you mean <i>AWS</i> cloud infra, right? <a href="https://github.com/iasql/iasql/blob/v0.1.1/package.json#L75-L103">https://github.com/iasql/iasql/blob/v0.1.1/package.json#L75-...</a>
This looks pretty interesting. How does IaSQL's approach to managing cloud infrastructure compare to traditional Infrastructure as Code (IaC) tools like Pulumi and Terraform, and what benefits can developers expect to see when using IaSQL?