Difference between revisions of "Terraform modules"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
Naming convention: <code>terraform-PROVICER-NAME</code> | Naming convention: <code>terraform-PROVICER-NAME</code> | ||
| − | |||
| − | |||
<code>module "[[vpc]]"</code> | <code>module "[[vpc]]"</code> | ||
<code>module "[[iam]]"</code> | <code>module "[[iam]]"</code> | ||
| − | <code>module "vm"</code> | + | <code>module "vm"</code> ([[terraform Libvirt module]]: https://registry.terraform.io/modules/MonolithProjects/vm/libvirt/latest) |
== Related terms == | == Related terms == | ||
Revision as of 20:59, 11 August 2021
This article is a Draft. Help us to complete it.
Naming convention: terraform-PROVICER-NAME
module "vpc"module "iam"module "vm"(terraform Libvirt module: https://registry.terraform.io/modules/MonolithProjects/vm/libvirt/latest)
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:
