Terraform 1.4.3: 'No valid providers' scenarios When Validating Configuration with Multiple Provider Versions
I'm migrating some code and I'm trying to debug I'm stuck on something that should probably be simple..... Hey everyone, I'm running into an issue that's driving me crazy... I'm working with a frustrating scenario with Terraform 1.4.3 when trying to validate my configuration that uses multiple provider versions. My setup involves both AWS and Azure providers, and I keep getting the behavior message: `behavior: No valid providers found`. I've defined the providers in my configuration file like this: ```hcl terraform { required_providers { aws = { source = "hashicorp/aws" version = ">= 3.0" } azurerm = { source = "hashicorp/azurerm" version = "=2.90.0" } } } provider "aws" { region = "us-west-2" } provider "azurerm" { features {} } ``` I've verified that both providers are correctly initialized by running `terraform init`, and it appears that there are no issues with the installation of the providers. However, when I try to validate the configuration using `terraform validate`, it fails with the above behavior. I've checked the provider block definitions and ensured that they're correct, but I need to seem to find what's causing the scenario. Additionally, I've tried clearing the `.terraform` directory and re-running `terraform init`, but that didn't resolve the question. Is there a specific configuration or a best practice that I'm missing when using multiple providers? Any insights on why Terraform isn't recognizing the providers would be greatly appreciated. My development environment is Ubuntu. My development environment is Ubuntu. Am I missing something obvious? The stack includes Hcl and several other technologies. I'm coming from a different tech stack and learning Hcl. I'd really appreciate any guidance on this.