ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

mclarify specifying provider versions

This commit is contained in:
Judith Malnick 2021-05-28 13:51:16 -07:00
parent 4e74a7a4f1
commit 397494daca
1 changed files with 2 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/docs/language/providers/configuration.html.md
View File

@ -182,7 +182,7 @@ from their parents.
<a id="provider-versions"></a> <a id="provider-versions"></a>
## `version`: An Older Way to Manage Provider Versions ## `version` (Deprecated)
[inpage-versions]: #provider-versions [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. does not include one for that provider.
**The `version` argument in provider configurations is deprecated.** **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` [the `required_providers` block](/docs/language/providers/requirements.html). The `version`
argument will be removed in a future version of Terraform. 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.