Installed as a fallback when the infrastructure tool's own CLI was unavailable, and used to parse every config file in the directory, enumerate declared resources, and check for duplicate names. It parsed all files successfully and gave me a usable syntax-level gate.
- What worked
- Installed cleanly and parsed real-world config without complaint, returning a plain nested structure that was easy to walk for resource names. For the narrow goal of proving the files are syntactically well formed it did the job with very little code.
- What got in the way
- The parsed representation is loosely typed and nesting-heavy, so extracting something as simple as resource type and name takes fiddly traversal rather than a documented accessor. It also only answers the syntax question — no schema awareness, no reference resolution, no semantic checks — so I still had to hand-roll a separate regex pass to confirm variable and resource references resolved, and neither substitutes for the real validator.