-
Notifications
You must be signed in to change notification settings - Fork 73
Add new local_command data source for running and retrieving data from local executables
#452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 24 commits
Commits
Show all changes
36 commits
Select commit
Hold shift + click to select a range
bd7aa5b
initial implementation
austinvalle 7025357
update the config directory to work running manually
austinvalle 232b910
add count
austinvalle bbe4230
add test
austinvalle 07aa729
add tests
austinvalle 2653d24
don't encode null arguments
austinvalle b1ca955
add copyright headers
austinvalle 9b226e4
add documentation and example
austinvalle 67c13fe
remove the tests temporarily for the CI
austinvalle f65ffa7
lint
austinvalle 9640fa9
use rc1 for generating docs
austinvalle d87fd02
add changelog and fix tests for windows
austinvalle 2b98309
add vscode gitignore
austinvalle 7e68f1a
refactor
austinvalle 3103be9
first draft of data source
austinvalle 945e12d
comments
austinvalle bcc4334
add stdout tests
austinvalle b9c3f88
refactor
austinvalle c7eb0ec
refactor + additional tests
austinvalle 483a428
add another test
austinvalle e207dfd
remove comment (not needed)
austinvalle 691c1f1
update docs on schema
austinvalle 21dd9c5
add example to docs
austinvalle 3c497b9
add changelog
austinvalle 85affd3
add doc comment
austinvalle 0bb679b
add invalid working directory test
austinvalle 112917d
Merge branch 'main' into av/local-exec-ds
austinvalle cc983c4
adjust OS specific tests
austinvalle b117e90
explicitly use absolute path, since windows is weird lol
austinvalle c5a258e
reverting
austinvalle b75aba5
Fix TF 0.13 errors
austinvalle e3f1139
use pwd command
austinvalle 7a61031
fix windows CI
austinvalle c54c7da
more WSL fixes
austinvalle 93d0089
skip for consistency
austinvalle 68f3a77
reformat comment
austinvalle File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| kind: FEATURES | ||
| body: 'action/local_command: New action that invokes an executable on the local machine.' | ||
| time: 2025-11-03T15:39:52.741799-05:00 | ||
| custom: | ||
| Issue: "450" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| kind: FEATURES | ||
| body: 'data/local_command: New data source that runs an executable on the local machine and returns the exit code, standard output data, and standard error data.' | ||
| time: 2025-11-06T18:01:54.341138-05:00 | ||
| custom: | ||
| Issue: "452" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,79 @@ | ||
| page_title: "local_command Action - terraform-provider-local" | ||
| subcategory: "" | ||
| description: |- | ||
| Invokes an executable on the local machine. All environment variables visible to the Terraform process are passed through to the child process. After the child process successfully executes, the stdout will be returned for Terraform to display to the user. | ||
| Any non-zero exit code will be treated as an error and will return a diagnostic to Terraform containing the stderr message if available. | ||
| --- | ||
|
|
||
| # local_command (Action) | ||
|
|
||
| Invokes an executable on the local machine. All environment variables visible to the Terraform process are passed through to the child process. After the child process successfully executes, the `stdout` will be returned for Terraform to display to the user. | ||
|
|
||
| Any non-zero exit code will be treated as an error and will return a diagnostic to Terraform containing the `stderr` message if available. | ||
|
|
||
| ## Example Usage | ||
|
|
||
| For the following bash script (`example_script.sh`): | ||
| ```bash | ||
| #!/bin/bash | ||
|
|
||
| DATA=$(</dev/stdin) | ||
| echo "stdin: $DATA, args: $@" | ||
| ``` | ||
|
|
||
| Here is an example configuration that will run the script after a resource is created: | ||
|
|
||
| ```terraform | ||
| resource "terraform_data" "test" { | ||
| lifecycle { | ||
| action_trigger { | ||
| events = [after_create] | ||
| actions = [action.local_command.bash_example] | ||
| } | ||
| } | ||
| } | ||
|
|
||
| action "local_command" "bash_example" { | ||
| config { | ||
| command = "bash" | ||
| arguments = ["example_script.sh", "arg1", "arg2"] | ||
| stdin = jsonencode({ | ||
| "key1" : "value1" | ||
| "key2" : "value2" | ||
| }) | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| The `stdout` will be displayed when the action is invoked: | ||
| ```bash | ||
| $ terraform apply -auto-approve | ||
|
|
||
| # .. Terraform CLI output truncated for example purposes | ||
|
|
||
| Plan: 1 to add, 0 to change, 0 to destroy. Actions: 1 to invoke. | ||
| terraform_data.test: Creating... | ||
| terraform_data.test: Creation complete after 0s [id=4b41b541-5550-590a-9949-657e91baa346] | ||
| Action started: action.local_command.bash_example (triggered by terraform_data.test) | ||
| Action action.local_command.bash_example (triggered by terraform_data.test): | ||
|
|
||
| stdin: {"key1":"value1","key2":"value2"}, args: arg1 arg2 | ||
|
|
||
|
|
||
| Action complete: action.local_command.bash_example (triggered by terraform_data.test) | ||
|
|
||
| Apply complete! Resources: 1 added, 0 changed, 0 destroyed. | ||
| ``` | ||
|
|
||
| <!-- action schema generated by tfplugindocs --> | ||
| ## Schema | ||
|
|
||
| ### Required | ||
|
|
||
| - `command` (String) Executable name to be discovered on the PATH or absolute path to executable. | ||
|
|
||
| ### Optional | ||
|
|
||
| - `arguments` (List of String) Arguments to be passed to the given command. Any `null` arguments will be removed from the list. | ||
| - `stdin` (String) Data to be passed to the given command's standard input. | ||
| - `working_directory` (String) The directory where the command should be executed. Defaults to the Terraform working directory. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| --- | ||
| # generated by https://github.com/hashicorp/terraform-plugin-docs | ||
| page_title: "local_command Data Source - terraform-provider-local" | ||
| subcategory: "" | ||
| description: |- | ||
| Runs an executable on the local machine and returns the exit code, standard output data (stdout), and standard error data (stderr). All environment variables visible to the Terraform process are passed through to the child process. Both stdout and stderr returned by this data source are UTF-8 strings, which can be decoded into Terraform values https://developer.hashicorp.com/terraform/language/expressions/types for use elsewhere in the Terraform configuration. There are built-in decoding functions such as jsondecode https://developer.hashicorp.com/terraform/language/functions/jsondecode or yamldecode https://developer.hashicorp.com/terraform/language/functions/yamldecode, and more specialized decoding functions https://developer.hashicorp.com/terraform/plugin/framework/functions/concepts can be built with a Terraform provider. | ||
| Any non-zero exit code returned by the command will be treated as an error and will return a diagnostic to Terraform containing the stderr message if available. If a non-zero exit code is expected by the command, set allow_non_zero_exit_code to true. | ||
| ~> Warning This mechanism is provided as an "escape hatch" for exceptional situations where a first-class Terraform provider is not more appropriate. Its capabilities are limited in comparison to a true data source, and implementing a data source via a local executable is likely to hurt the portability of your Terraform configuration by creating dependencies on external programs and libraries that may not be available (or may need to be used differently) on different operating systems. | ||
| ~> Warning HCP Terraform and Terraform Enterprise do not guarantee availability of any particular language runtimes or external programs beyond standard shell utilities, so it is not recommended to use this data source within configurations that are applied within either. | ||
| --- | ||
|
|
||
| # local_command (Data Source) | ||
|
|
||
| Runs an executable on the local machine and returns the exit code, standard output data (`stdout`), and standard error data (`stderr`). All environment variables visible to the Terraform process are passed through to the child process. Both `stdout` and `stderr` returned by this data source are UTF-8 strings, which can be decoded into [Terraform values](https://developer.hashicorp.com/terraform/language/expressions/types) for use elsewhere in the Terraform configuration. There are built-in decoding functions such as [`jsondecode`](https://developer.hashicorp.com/terraform/language/functions/jsondecode) or [`yamldecode`](https://developer.hashicorp.com/terraform/language/functions/yamldecode), and more specialized [decoding functions](https://developer.hashicorp.com/terraform/plugin/framework/functions/concepts) can be built with a Terraform provider. | ||
|
|
||
| Any non-zero exit code returned by the command will be treated as an error and will return a diagnostic to Terraform containing the `stderr` message if available. If a non-zero exit code is expected by the command, set `allow_non_zero_exit_code` to `true`. | ||
|
|
||
| ~> **Warning** This mechanism is provided as an "escape hatch" for exceptional situations where a first-class Terraform provider is not more appropriate. Its capabilities are limited in comparison to a true data source, and implementing a data source via a local executable is likely to hurt the portability of your Terraform configuration by creating dependencies on external programs and libraries that may not be available (or may need to be used differently) on different operating systems. | ||
|
|
||
| ~> **Warning** HCP Terraform and Terraform Enterprise do not guarantee availability of any particular language runtimes or external programs beyond standard shell utilities, so it is not recommended to use this data source within configurations that are applied within either. | ||
|
|
||
| ## Example Usage | ||
|
|
||
| ```terraform | ||
| // A toy example using the JSON utility `jq` to process Terraform data | ||
| // https://jqlang.org/ | ||
| data "local_command" "filter_fruit" { | ||
| command = "jq" | ||
| stdin = jsonencode([{ name = "apple" }, { name = "lemon" }, { name = "apricot" }]) | ||
| arguments = [".[:2] | [.[].name]"] # Grab the first two fruit names from the list | ||
| } | ||
|
|
||
| output "fruit_tf" { | ||
| value = jsondecode(data.local_command.filter_fruit.stdout) | ||
| } | ||
|
|
||
| # Outputs: | ||
| # | ||
| # fruit_tf = [ | ||
| # "apple", | ||
| # "lemon", | ||
| # ] | ||
| ``` | ||
|
|
||
| <!-- schema generated by tfplugindocs --> | ||
| ## Schema | ||
|
|
||
| ### Required | ||
|
|
||
| - `command` (String) Executable name to be discovered on the PATH or absolute path to executable. | ||
|
|
||
| ### Optional | ||
|
|
||
| - `allow_non_zero_exit_code` (Boolean) Indicates that the command returning a non-zero exit code should be treated as a successful execution. Further assertions can be made of the `exit_code` value with the [`check` block](https://developer.hashicorp.com/terraform/language/block/check). Defaults to false. | ||
| - `arguments` (List of String) Arguments to be passed to the given command. Any `null` arguments will be removed from the list. | ||
| - `stdin` (String) Data to be passed to the given command's standard input as a UTF-8 string. [Terraform values](https://developer.hashicorp.com/terraform/language/expressions/types) can be encoded by any Terraform encode function, for example, [`jsonencode`](https://developer.hashicorp.com/terraform/language/functions/jsonencode). | ||
| - `working_directory` (String) The directory where the command should be executed. Defaults to the Terraform working directory. | ||
|
|
||
| ### Read-Only | ||
|
|
||
| - `exit_code` (Number) The exit code returned by the command. By default, if the exit code is non-zero, the data source will return a diagnostic to Terraform. If a non-zero exit code is expected by the command, set `allow_non_zero_exit_code` to `true`. | ||
| - `stderr` (String) Data returned from the command's standard error stream. The data is returned directly from the command as a UTF-8 string and will be populated regardless of the exit code returned. | ||
| - `stdout` (String) Data returned from the command's standard output stream. The data is returned directly from the command as a UTF-8 string, which can then be decoded by any Terraform decode function, for example, [`jsondecode`](https://developer.hashicorp.com/terraform/language/functions/jsondecode). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| resource "terraform_data" "test" { | ||
| lifecycle { | ||
| action_trigger { | ||
| events = [after_create] | ||
| actions = [action.local_command.bash_example] | ||
| } | ||
| } | ||
| } | ||
|
|
||
| action "local_command" "bash_example" { | ||
| config { | ||
| command = "bash" | ||
| arguments = ["example_script.sh", "arg1", "arg2"] | ||
| stdin = jsonencode({ | ||
| "key1" : "value1" | ||
| "key2" : "value2" | ||
| }) | ||
| } | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| #!/bin/bash | ||
|
|
||
| DATA=$(</dev/stdin) | ||
| echo "stdin: $DATA, args: $@" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| // A toy example using the JSON utility `jq` to process Terraform data | ||
| // https://jqlang.org/ | ||
| data "local_command" "filter_fruit" { | ||
| command = "jq" | ||
| stdin = jsonencode([{ name = "apple" }, { name = "lemon" }, { name = "apricot" }]) | ||
| arguments = [".[:2] | [.[].name]"] # Grab the first two fruit names from the list | ||
| } | ||
|
|
||
| output "fruit_tf" { | ||
| value = jsondecode(data.local_command.filter_fruit.stdout) | ||
| } | ||
|
|
||
| # Outputs: | ||
| # | ||
| # fruit_tf = [ | ||
| # "apple", | ||
| # "lemon", | ||
| # ] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.