From 397494dacaab85fe8b2d9c52f4356978c9c76e8a Mon Sep 17 00:00:00 2001 From: Judith Malnick Date: Fri, 28 May 2021 13:51:16 -0700 Subject: [PATCH] mclarify specifying provider versions --- website/docs/language/providers/configuration.html.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/website/docs/language/providers/configuration.html.md b/website/docs/language/providers/configuration.html.md index 20cc28dcb..d5cf3f1b4 100644 --- a/website/docs/language/providers/configuration.html.md +++ b/website/docs/language/providers/configuration.html.md @@ -182,7 +182,7 @@ from their parents. -## `version`: An Older Way to Manage Provider Versions +## `version` (Deprecated) [inpage-versions]: #provider-versions @@ -193,11 +193,6 @@ constraint in a provider configuration is only used if `required_providers` does not include one for that provider. **The `version` argument in provider configurations is deprecated.** -In Terraform 0.13 and later, version constraints should always be declared in +In Terraform 0.13 and later, always declare provider version constraints in [the `required_providers` block](/docs/language/providers/requirements.html). The `version` argument will be removed in a future version of Terraform. - --> **Note:** The `version` meta-argument made sense before Terraform 0.13, since -Terraform could only install providers that were distributed by HashiCorp. Now -that Terraform can install providers from multiple sources, it makes more sense -to keep version constraints and provider source addresses together.