Difference between revisions of "Terraform provider versioning"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* [[Terraform Associate]]: Handle Terraform and [[Terraform provider|provider installation]] and versioning | * [[Terraform Associate]]: Handle Terraform and [[Terraform provider|provider installation]] and versioning | ||
| − | terraform { | + | [[Terraform block|terraform]] { |
required_providers { | required_providers { | ||
aws = "~> 1.2.0" | aws = "~> 1.2.0" | ||
Revision as of 00:00, 28 February 2022
https://www.terraform.io/language/providers/configuration#version-deprecated since Terraform 0.13 (August 2020)
- Terraform Associate: Handle Terraform and provider installation and versioning
terraform { required_providers { aws = "~> 1.2.0" } }
Related
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:
