Adding provider constraint best practice statement (#32697)

* Adding provider constraint best practice

Originally communicated here, this statement is missing in newer docs.

https://developer.hashicorp.com/terraform/language/v1.1.x/configuration-0-11/providers?ajs_aid=3cf1bdca-a598-4dc5-b074-6064b276abb6&_gl=1*xuizrx*_ga*MTM1ODg4NTcyMi4xNjY2MTA5NjI1*_ga_P7S46ZYEKW*MTY3NjU2OTMzNS4zMi4wLjE2NzY1Njk0MDMuMC4wLjA.&product_intent=terraform#provider-versions

* Update website/docs/language/providers/index.mdx

Co-authored-by: Judith Malnick <judith@hashicorp.com>

---------

Co-authored-by: Judith Malnick <judith@hashicorp.com>
This commit is contained in:
Amanda B 2023-02-27 12:22:07 -05:00 committed by GitHub
parent 729408333e
commit 93f9cff99f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -55,6 +55,8 @@ see the [provider publishing documentation](/terraform/registry/providers/docs).
## How to Use Providers
Providers are released separately from Terraform itself, and have their own version numbers. In production we recommend constraining the acceptable provider versions in the configuration's provider requirements block, to make sure that `terraform init` does not install newer versions of the provider that are incompatible with the configuration.
To use resources from a given provider, you need to include some information
about it in your configuration. See the following pages for details: