Difference between revisions of "Terraform blocks"
Jump to navigation
Jump to search
↑ https://www.hashicorp.com/blog/terraform-1-1-improves-refactoring-and-the-cloud-cli-experience
| Line 14: | Line 14: | ||
* <code>[[required_version]]</code> | * <code>[[required_version]]</code> | ||
* <code>[[var.]]</code> | * <code>[[var.]]</code> | ||
| + | * <code>[[Error: Reserved block type in a module block]]</code> | ||
== See also == | == See also == | ||
Revision as of 14:27, 17 October 2022
Block types:
terraform- Terraform module blocks:
module - Terraform resource blocks:
resource - Terraform dynamic blocks:
dynamic - Terraform cloud block:
cloud(Dec 2021) Terraform 1.1 [1] - Terraform data blocks:
data - Terraform local blocks:
local - Terraform provisioner blocks:
provisioner - Terraform providers:
provider
Related
See also
- Terraform blocks:
terraform, cloud, moved, dynamic, Terraform import block,required_providers - 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:
