You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initializing modules...
- k3s in modules/k3s
Initializing the backend...
Initializing provider plugins...
- Finding hashicorp/helm versions matching "2.2.0"...
- Finding latest version of hashicorp/civo...
- Finding hashicorp/null versions matching "3.1.0"...
- Finding civo/civo versions matching "0.10.9"...
- Finding hashicorp/kubernetes versions matching "2.4.1"...
- Installing hashicorp/helm v2.2.0...
- Installed hashicorp/helm v2.2.0 (signed by HashiCorp)
- Installing hashicorp/null v3.1.0...
- Installed hashicorp/null v3.1.0 (signed by HashiCorp)
- Installing civo/civo v0.10.9...
- Installed civo/civo v0.10.9 (signed by a HashiCorp partner, key ID CA1DE390990EBE66)
- Installing hashicorp/kubernetes v2.4.1...
- Installed hashicorp/kubernetes v2.4.1 (signed by HashiCorp)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
╷
│ Error: Failed to query available provider packages
│
If you try to run without custom module things work as expected.
When trying to use
civo/civo
provider with custom module results in the module being searched underhashicorp/civo
and the module is not initialised.Clone the reproducer https://github.com/kameshsampath/civo-example and doing
terraform init
will result in the following error:If you try to run without custom module things work as expected.
CC: @saiyam1814 @alejandrojnm
The text was updated successfully, but these errors were encountered: