diff --git a/website/docs/configuration/blocks/providers/index.html.md b/website/docs/configuration/blocks/providers/index.html.md index 81ef9f094..287eb6539 100644 --- a/website/docs/configuration/blocks/providers/index.html.md +++ b/website/docs/configuration/blocks/providers/index.html.md @@ -69,6 +69,8 @@ and commit it to version control along with your configuration. If a lock file is present, Terraform Cloud, CLI, and Enterprise will all obey it when installing providers. +> **Hands-on:** Try the [Lock and Upgrade Provider Versions](https://learn.hashicorp.com/tutorials/terraform/provider-versioning?in=terraform/configuration-language&utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) tutorial on HashiCorp Learn. + ## How to Find Providers To find providers for the infrastructure platforms you use, browse diff --git a/website/docs/configuration/dependency-lock.html.md b/website/docs/configuration/dependency-lock.html.md index c65902ba1..9b516d753 100644 --- a/website/docs/configuration/dependency-lock.html.md +++ b/website/docs/configuration/dependency-lock.html.md @@ -9,6 +9,8 @@ page_title: "Dependency Lock File (.terraform.lock.hcl) - Configuration Language versions of Terraform did not track dependency selections at all, so the information here is not relevant to those versions. +> **Hands-on:** Try the [Lock and Upgrade Provider Versions](https://learn.hashicorp.com/tutorials/terraform/provider-versioning?in=terraform/configuration-language&utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) tutorial on HashiCorp Learn. + A Terraform configuration may refer to two different kinds of external dependency that come from outside of its own codebase: diff --git a/website/docs/configuration/provider-requirements.html.md b/website/docs/configuration/provider-requirements.html.md index ba613e86f..40ca196da 100644 --- a/website/docs/configuration/provider-requirements.html.md +++ b/website/docs/configuration/provider-requirements.html.md @@ -217,6 +217,15 @@ The `version` argument is optional; if omitted, Terraform will accept any version of the provider as compatible. However, we strongly recommend specifying a version constraint for every provider your module depends on. +To ensure Terraform always installs the same provider versions for a given +configuration, you can use Terraform CLI to create a +[dependency lock file](/docs/configuration/dependency-lock.html) +and commit it to version control along with your configuration. If a lock file +is present, Terraform Cloud, CLI, and Enterprise will all obey it when +installing providers. + +> **Hands-on:** Try the [Lock and Upgrade Provider Versions](https://learn.hashicorp.com/tutorials/terraform/provider-versioning?in=terraform/configuration-language&utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) tutorial on HashiCorp Learn. + ### Best Practices for Provider Versions Each module should at least declare the minimum provider version it is known