dflook/terraform-remote-state

Retrieves the root-level outputs from a Terraform remote state.

View on GitHub

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Maintainedlast commit Jan 13, 2026
License: None

Pinned Snippet

workflow.ymlSHA-pinned

uses: dflook/terraform-remote-state@30e277d4cb2e0bb07d7682e9a60b3d969cd178cf # v2.2.3

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

Inputs

name	description	required	default
backend_type	The name of the Terraform plugin used for backend state	yes	—
workspace	Terraform workspace to get the outputs for	no	default
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	""

Outputs

name	description
json_output_path	This is the path to all the root module outputs in a JSON file. The path is relative to the Actions workspace. For example, with the Terraform config: ```hcl output "service_hostname" { value = "example.com" } ``` The file pointed to by this output will contain: ```json { "service_hostname": "example.com" } ``` Terraform list, set and tuple types are cast to a JSON array, map and object types are cast to a JSON object.

name

description

json_output_path

This is the path to all the root module outputs in a JSON file. The path is relative to the Actions workspace. For example, with the Terraform config: ```hcl output "service_hostname" { value = "example.com" } ``` The file pointed to by this output will contain: ```json { "service_hostname": "example.com" } ``` Terraform list, set and tuple types are cast to a JSON array, map and object types are cast to a JSON object.