Action-terraform-validate
A GitHub Action that runs terraform validate to statically check Terraform and OpenTofu modules in continuous integration (CI) workflows.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
49/100 Fair
- Maintained
- 88last commit 61 days ago
- Popular
- 187 GitHub stars
- Easy to install
- 100 install platforms, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
- GitHub stars
- 7
- Open issues
- 1
- Last commit
- 2026-09-21
- Latest release
- v1.0.6
- License
- MIT
- Activity
- stale
Checked 16 days ago - source: GitHub (devops-infra/action-terraform-validate)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
No first-install notes yet.
Variants
Alternatives
No alternatives collected yet.
Common questions
Does action-terraform-validate confirm that Terraform has been applied?
No. Terraform validate only checks syntax and structure, not the applied state.
How are root variables handled during Terraform validation?
Terraform validate checks module validity independently of plan options. It treats root input variables as unknown because variables are supplied during planning.
What self-hosted GitHub runner issue can affect Terraform setup?
The setup-terraform@v3 action can start failing with an AggregateError when invoked within a self-hosted GitHub Actions runner.
Why might Terraform validate fail with an obscure error in a GitHub Action?
The Terraform process can exit with status code 137, which suggests it is being killed by GitHub resource limits. Disabling the setup-terraform wrapper can reveal this exit code.
Answers sourced from discuss.hashicorp.com, github.com, stackoverflow.com, www.reddit.com
Community
- Need Terraform Validation : r/Terraform - Reddit (reddit)
- `terraform validate` doesn't (and does) work with variable validations (forum)
- Why are TF validate and plan so shallow? What can I do about it? (reddit)
- Behavior of `module.output` in the `terraform validate` command (forum)
- `terraform validate` fails on GitHub Action with obscure error message (forum)
Collected 48 days ago - public community threads