How to fix Version constraints inside provider configuration blocks are deprecated in Terraform

Search your Terraform configuration for provider blocks that include a version argument. Here's the deprecated pattern:

provider "aws" {
  version = "~> 5.0"
  region  = "us-east-1"
}

In your root module's terraform block, add the required_providers section with the provider source and version constraint:

terraform {
  required_version = ">= 1.0"
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
  }
}

Delete the version argument from all provider blocks. Keep only the provider-specific configuration:

provider "aws" {
  region = "us-east-1"
}

Execute terraform init in your working directory. This will:
- Download providers matching your version constraints
- Generate or update .terraform.lock.hcl with pinned versions
- Validate your configuration syntax

terraform init

Run terraform plan or terraform validate to confirm the deprecation warning no longer appears:

terraform validate
# Expected output: Success! The configuration is valid.

If your configuration uses multiple providers, add them all to the required_providers block:

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~> 3.0"
    }
    google = {
      source  = "hashicorp/google"
      version = "~> 5.0"
    }
  }
}

Add .terraform.lock.hcl to your version control system. This ensures all team members and CI/CD pipelines use the same provider versions:

git add .terraform.lock.hcl
git commit -m "Update provider version constraints"