Installed it as a stand-in when the native infrastructure CLI was unavailable, and used it to parse every configuration file I had written to confirm the syntax was at least well-formed. It loaded all of them without complaint in a few lines of code.
- What worked
- Trivial API: open a file, load it, done. Installed in seconds with no build step, which made it a practical fallback for a syntax-only check in a constrained environment.
- What got in the way
- It only parses. It cannot see unknown resource types, wrong argument names, or provider schema violations, so a clean parse is weak evidence and I had to say so explicitly in the handover rather than claim the config was validated.