New Terraform Tutorial: Lock and Upgrade Provider Versions
Learn to manage your provider versions with this new tutorial on HashiCorp Learn.
When multiple users or automation tools manage the same Terraform configuration, they should use the same versions of the configuration’s required providers.
» Manage Provider Versions
There are two ways for you to manage provider versions in your configuration:
- Specify provider version constraints in your configuration’s
terraform
block, or - Use the dependency lock file (introduced in Terraform 0.14)
If you do not scope provider versions, Terraform will download the latest version. This may lead to unexpected infrastructure changes. By specifying carefully scoped provider versions and using the dependency lock file, you ensure that Terraform uses the correct provider version to consistently manage your configuration.
The new tutorial, Lock and Upgrade Provider Versions, will guide you through how to manage provider versioning using both of these methods. In the tutorial, you will create an S3 bucket from an initialized Terraform configuration and upgrade the AWS provider to use the latest version.
![View of Lock and Upgrade Provider Versions tutorial](/_next/image?url=https%3A%2F%2Fwww.datocms-assets.com%2F2885%2F1614368125-tfpattern4.png&w=3840&q=75)
By the end of this tutorial, you will understand how to use the dependency lock file to ensure consistent Terraform runs across multiple users and automation tools.
» Learn More
Get more hands-on experience with writing Terraform configurations with this collection of tutorials on HashiCorp Learn.
Sign up for the latest HashiCorp news
More blog posts like this one
![Terraform extension for VS Code speeds up loading of large workspaces](/_next/image?url=https%3A%2F%2Fwww.datocms-assets.com%2F2885%2F1714155806-blog-library-product-terraform-dark-gradient.jpg&w=3840&q=75)
Terraform extension for VS Code speeds up loading of large workspaces
New releases of the HashiCorp Terraform extension for Visual Studio Code and Terraform language server significantly reduce memory usage and start up time for large workspaces.
![Why use Vault-backed dynamic credentials to secure HCP Terraform infrastructure?](/_next/image?url=https%3A%2F%2Fwww.datocms-assets.com%2F2885%2F1572286031-vault-terraform-background.png&w=1920&q=75)
Why use Vault-backed dynamic credentials to secure HCP Terraform infrastructure?
Learn how HCP Terraform and Terraform Enterprise users can use Vault-backed dynamic credentials to secure their infrastructure during provisioning better than the base-level dynamic provider credentials.
![HCP Terraform adds granular API access for audit trails](/_next/image?url=https%3A%2F%2Fwww.datocms-assets.com%2F2885%2F1714170900-blog-library-product-hcp-terraform-dark.jpg&w=3840&q=75)
HCP Terraform adds granular API access for audit trails
HCP Terraform eliminates the need to rely on organization permissions to the audit trails endpoint, streamlining permissions workflows and reducing risk.