Difference between revisions of "Terraform examples"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
== Terraform native == | == Terraform native == | ||
| − | * [[Terraform: Hello world.tf]] (<code>output</code>) | + | * [[Terraform: Hello world.tf]] (<code>[[output]]</code>) |
| − | * [[Terraform: read files]] (<code>file</code>) | + | * [[Terraform: read files]] (<code>[[file]]</code>) |
== AWS provider == | == AWS provider == | ||
Revision as of 16:05, 6 September 2021
Terraform native
AWS provider
- AWS instance example with aws_ami lookup and key_name:
aws instance,aws_ami - AWS instance example with aws_ami lookup:
aws instance,aws_ami - AWS instance example: main.tf:
aws instance
VMware provider
- VMware: https://registry.terraform.io/providers/hashicorp/vsphere/latest/docs/resources/virtual_machine
Related terms
See also
- 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:
