actions-marketplace-validations/terraform-check

Check if there are Terraform changes to apply

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/dflook_terraform-check@8abe57e9caec11de4046a8e9bcc74bb467e33478 # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
path	Path to the Terraform root module to check	no	.
workspace	Terraform workspace to run the plan in	no	default
variables	Variables to set for the terraform plan. This should be valid Terraform syntax - like a [variable definition file](https://developer.hashicorp.com/terraform/language/values/variables#variable-definitions-tfvars-files). Variables set here override any given in `var_file`s.	no	—
var_file	List of tfvars files to use, one per line. Paths should be relative to the GitHub Actions workspace	no	—
backend_config	List of Terraform backend config values, one per line.	no	""
backend_config_file	List of Terraform backend config files to use, one per line. Paths should be relative to the GitHub Actions workspace	no	""
parallelism	Limit the number of concurrent operations	no	0

name	description
failure-reason	When the job outcome is `failure` because the there are outstanding changes to apply, this will be set to 'changes-to-apply'. If the job fails for any other reason this will not be set. This can be used with the Actions expression syntax to conditionally run a step when there are changes to apply.