Terraform providers manage resources by communicating between Terraform and target APIs. Whenever the target APIs change or add functionality, provider maintainers may update and version the provider.
When multiple users or automation tools run the same Terraform configuration, they should all use the same versions of their required providers.
If you do not scope provider version appropriately, Terraform will download the latest provider version that fulfills the version constraint. This may lead to unexpected infrastructure changes. By specifying carefully scoped provider versions and using the dependency lock file, you can ensure Terraform is using the correct provider version so your configuration is applied consistently.
The version argument is used to constrain the provider to a specific version or a range of versions in order to prevent downloading a new provider that may possibly contain breaking changes. If the version isn’t specified, Terraform will automatically download the most recent provider during
initialization. While you can specify the version of the provider in the provider block for now, that syntax has been deprecated and will be removed in a future version. HashiCorp recommends that you create a required_providers block for Terraform configuration.
Terraform 0.14 introduced a lock file that is generated when terraform init is run for the first time on a configuration. The lock file is named .terrafom.lock.hcl, and it records the version of each provider being used in the configuration. This file can be checked into source control, and provides a consistent experience for everyone using the configuration. Terraform will continue to use the provider versions specified in the lock file, unless you run terraform init -upgrade. Terraform will then update the plugins to the latest version that matches the constraints specified in the required_providers block and update the lock file with the new versions.
Visit us - networknuts.net
Facebook - /networknuts
Instagram - /networknuts