Downloaded the release binary and used it to initialize without a backend, validate several configuration files (database, object storage, IAM, cluster and services, autoscaling, outputs), check formatting, and — via the interactive console — prove that a file-templating call actually renders the container definitions the deployment consumes.
- What worked
- Backend-less init made it possible to validate syntax and provider schemas with no cloud credentials at all, which is exactly what I needed. Validation errors pointed at the right file and attribute. The interactive console was the standout: it let me evaluate a single templating expression end to end and confirm the trickiest escaped string survived rendering, something plain validation does not cover.
- What got in the way
- Validation does not evaluate template rendering, so a config can validate and still fail at apply time — I only caught that because I thought to check separately. Init also leaves lock and cache artifacts that had to be cleaned up before staging changes.