Difference between revisions of "Terraform: output"
Jump to navigation
Jump to search
| (15 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | https://www.terraform.io/docs/language/values/outputs.html | |
| + | * A child module can use outputs to expose a subset of its resource attributes to a parent module. | ||
| + | * A root module can use outputs to print certain values in the CLI output after running terraform apply. | ||
| + | * When using [[remote state]], root module outputs can be accessed by other configurations via a terraform_remote_state data source. | ||
| + | * An output block can include a [[precondition]] block. | ||
| + | |||
| + | == Examples == | ||
| + | === Official example === | ||
output "instance_ip_addr" { | output "instance_ip_addr" { | ||
| − | value = [[aws_instance]].server.private_ip | + | value = [[aws_instance]].[[server.private_ip]] |
| + | } | ||
| + | |||
| + | === Additional examples === | ||
| + | output "your_output_value" { | ||
| + | value = XXXX | ||
} | } | ||
| + | |||
| + | Using sensitive value will not be printed on screen but will still be recorded in the state files. | ||
| + | [[sensitive]] = true | ||
| + | |||
| + | * <code>[[depends_on]]</code> | ||
== Related terms == | == Related terms == | ||
| Line 10: | Line 27: | ||
* [[Cloudformation]] | * [[Cloudformation]] | ||
* [[Terraform variables]] | * [[Terraform variables]] | ||
| + | * <code>[[output.tf]]</code> | ||
| + | * [[Terraform: Data sources]] | ||
| + | * [[Outputs: (CloudFormation)]] | ||
| + | |||
| + | == Activities == | ||
| + | * Read https://medium.com/@badawekoo/passing-variables-between-terraform-modules-using-implicit-dependency-e63194e98261 | ||
== See also == | == See also == | ||
Latest revision as of 08:12, 20 April 2023
https://www.terraform.io/docs/language/values/outputs.html
- A child module can use outputs to expose a subset of its resource attributes to a parent module.
- A root module can use outputs to print certain values in the CLI output after running terraform apply.
- When using remote state, root module outputs can be accessed by other configurations via a terraform_remote_state data source.
- An output block can include a precondition block.
Contents
Examples[edit]
Official example[edit]
output "instance_ip_addr" {
value = aws_instance.server.private_ip
}
Additional examples[edit]
output "your_output_value" {
value = XXXX
}
Using sensitive value will not be printed on screen but will still be recorded in the state files.
sensitive = true
Related terms[edit]
- Data source
- Cloudformation
- Terraform variables
output.tf- Terraform: Data sources
- Outputs: (CloudFormation)
Activities[edit]
See also[edit]
- Terraform, OpenTofu, Terrakube.org, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals:
depends_on, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type,TF_VAR_, TF_LOG, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog,tfsec, tflint, Operators, Expressions:for, splat, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos
Advertising:
