# Action-terraform-validate

Action-terraform-validate is a self-hosted development app. A GitHub Action that runs terraform validate to statically check Terraform and OpenTofu modules in continuous integration (CI) workflows. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/6027/action-terraform-validate

## Description

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.

## Health score

49/100 (Fair), based on 3 of 4 factors.
- Maintained: 88 (last commit 61 days ago)
- Popular: 18 (7 GitHub stars)
- Easy to install: 10 (0 install platforms, Docker image)

## Links

- Docker Hub: https://hub.docker.com/r/devopsinfra/action-terraform-validate
- Official website: https://shyper.pro
- GitHub: https://github.com/devops-infra/action-terraform-validate

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/6027/action-terraform-validate), the self-hosted and open-source app directory.
