shell_script | Resources | terr4m shell - Terraform Registry shell_script (Resource) The Shell script resource (shell_script) allows you to execute arbitrary commands as part of a Terraform lifecycle All commands must output a JSON string to the file defined by the TF_SCRIPT_OUTPUT environment variable and the file must be consistent on re-reading
Terraform Registry Registry Please enable Javascript to use this application
Data Sources | hashicorp external - Terraform Registry The external data source allows an external program implementing a specific protocol (defined below) to act as a data source, exposing arbitrary data for use elsewhere in the Terraform configuration Warning This mechanism is provided as an "escape hatch" for exceptional situations where a first-class Terraform provider is not more appropriate
genesyscloud_script | Resources - Terraform Registry script_name (String) Display name for the script A reliably unique name is recommended Updating this field will result in the script being dropped and recreated with a new GUID Optional division_id (String) Specify division id file_content_hash (String) Hash value of the script file content Used to detect changes
terraform-google-modules gcloud google | script_example Example . . . This example illustrates how to use the gcloud module with a script Inputs Outputs No outputs To provision this example, run the following from within this directory: terraform init to get the plugins terraform plan to see the infrastructure plan terraform apply to apply the infrastructure build terraform destroy to destroy the built
databricks_global_init_script | Resources - Terraform Registry Global init script in the Databricks workspace would only be changed, if Terraform stage did change This means that any manual changes to managed global init script won't be overwritten by Terraform, if there's no local change to source
aws_autoscaling_group | Resources - Terraform Registry Terraform has two types of ways you can add lifecycle hooks - via the initial_lifecycle_hook attribute from this resource, or via the separate aws_autoscaling_lifecycle_hook resource initial_lifecycle_hook exists here because any lifecycle hooks added with aws_autoscaling_lifecycle_hook will not be added until the Auto Scaling Group has been
shell_script | Data Sources - Terraform Registry shell_script The simplest example is the data source which implements only Read() Any output to stdout or stderr will show up in the logs, but to save state, you must output a JSON payload to stdout The last JSON object printed to stdout will be taken to be the output state