cuelm VS terraform-config-inspect

We've started working on a tool to use CUE to create a single config space across TF, Helm, and other tools in the devops space.

https://github.com/hofstadter-io/cuelm

Our hypothesis is that a unified config space across our industry will bring many benefits.

Our open questions are largely around whether we

(1) replace / alternative

(2) just a skin, still same reconciliation loop from the tools

(3) replace, but support existing modules & charts

Thanks for the share! Very timely

We are in the process of introspecting TF to produce CUE schemas. Maybe this can help us cuetify user TF as well

if you are curious: https://github.com/hofstadter-io/cuelm (it has expanded in scope since inception to include the likes of TF and other areas of e2e CI)

CDKTF currently generates .tf.json files which could be amenable to quite simplistic analysis of just whether there's a top-level resource property in the JSON at all. However, I don't think it's part of CDKTF's contract that it will always generate a single .tf.json file forever, so you might prefer to instead use terraform-config-inspect to analyze the generated configuration.

For situations where you just need the metadata about objects in a module I would suggest using terraform-config-inspect, which is a library maintained by the Terraform team that can read metadata about modules written for Terraform versions going back to Terraform v0.10, encapsulating the specific HCL details.

There is this tool terraform-config-inspect – it generally does what I'm thinking of but seems to have one major flaw for my use case: the attributes are ommitted, there is just the high level structure.