I don't think provider should be defined in the parent module

[clouda3]

That's not the right thing,we have to do this again and again

variable "profile" {
default = "course"
}
variable "region" {
default = "cn-beijing"
}

provider "alicloud" {
region = var.region
profile = var.profile
}

module "ecs_example" {
.......
source = "alibaba/ecs-instance/alicloud"

If we defined provider in our code ,we should not do this again if parent module did not define provider ,I think this is a legacy design issue,i checked aws module,they did the right thing,no provider defined in parent module
profile = var.profile

region = var.region
......

}

[zhamdoctor]

dude,when i add provider in my tf file,terraform init download not only aliyun/alicloud but also hashicorp/alicloud,it causes error,how to resolve this?

[clouda3]

use alias ,check the following documents

please refer this document :

terraform {
required_providers {
mycloud = {
source = "mycorp/mycloud"
version = "~> 1.0"
configuration_aliases = [ mycloud.alternate ]
}
}
}
Copy
»Default Provider Configurations
A provider block without an alias argument is the default configuration for that provider. Resources that don't set the provider meta-argument will use the default provider configuration that matches the first word of the resource type name. (For example, an aws_instance resource uses the default aws provider configuration unless otherwise stated.)

If every explicit configuration of a provider has an alias, Terraform uses the implied empty configuration as that provider's default configuration. (If the provider has any required configuration arguments, Terraform will raise an error when resources default to the empty configuration.)

[zhamdoctor]

use alias ,check the following documents

please refer this document :

terraform { required_providers { mycloud = { source = "mycorp/mycloud" version = "~> 1.0" configuration_aliases = [ mycloud.alternate ] } } } Copy »Default Provider Configurations A provider block without an alias argument is the default configuration for that provider. Resources that don't set the provider meta-argument will use the default provider configuration that matches the first word of the resource type name. (For example, an aws_instance resource uses the default aws provider configuration unless otherwise stated.)

If every explicit configuration of a provider has an alias, Terraform uses the implied empty configuration as that provider's default configuration. (If the provider has any required configuration arguments, Terraform will raise an error when resources default to the empty configuration.)

is there any example with alicloud?including arn authentication and encrypted secret/passwd.i definitly write provider in every tf file,but failed again. also，profile="default" was set

[clouda3]

use alias ,check the following documents
please refer this document :
terraform { required_providers { mycloud = { source = "mycorp/mycloud" version = "~> 1.0" configuration_aliases = [ mycloud.alternate ] } } } Copy »Default Provider Configurations A provider block without an alias argument is the default configuration for that provider. Resources that don't set the provider meta-argument will use the default provider configuration that matches the first word of the resource type name. (For example, an aws_instance resource uses the default aws provider configuration unless otherwise stated.)
If every explicit configuration of a provider has an alias, Terraform uses the implied empty configuration as that provider's default configuration. (If the provider has any required configuration arguments, Terraform will raise an error when resources default to the empty configuration.)

is there any example with alicloud?including arn authentication and encrypted secret/passwd.i definitly write provider in every tf file,but failed again. also，profile="default" was set

Sorry bro,I still dont know ,this is why I posted here last year,nobody fix this problem