Error while installing hashicorp/create: provider registry

Terraform
1

Hi All,

I was trying to use helm provider for eks and i am getting error during terraform init

Initializing provider plugins…

  • Finding latest version of hashicorp/create…
  • Finding latest version of hashicorp/aws…
  • Finding latest version of hashicorp/archive…
  • Finding latest version of hashicorp/helm…
  • Installing hashicorp/aws v3.22.0…
  • Installed hashicorp/aws v3.22.0 (signed by HashiCorp)
  • Installing hashicorp/archive v2.0.0…
  • Installed hashicorp/archive v2.0.0 (signed by HashiCorp)
  • Installing hashicorp/helm v2.0.1…
  • Installed hashicorp/helm v2.0.1 (signed by HashiCorp)

Error: Failed to install provider

Error while installing hashicorp/create: provider registry
registry.terraform.io does not have a provider named
registry.terraform.io/hashicorp/create

below error during terraform v0.14

Initializing provider plugins…

  • Finding latest version of hashicorp/create…
  • Finding latest version of hashicorp/aws…
  • Finding latest version of hashicorp/archive…
  • Finding latest version of hashicorp/helm…
  • Installing hashicorp/aws v3.22.0…
  • Installed hashicorp/aws v3.22.0 (signed by HashiCorp)
  • Installing hashicorp/archive v2.0.0…
  • Installed hashicorp/archive v2.0.0 (signed by HashiCorp)
  • Installing hashicorp/helm v2.0.1…
  • Installed hashicorp/helm v2.0.1 (signed by HashiCorp)

Error: Failed to install provider

Error while installing hashicorp/create: provider registry
registry.terraform.io does not have a provider named
registry.terraform.io/hashicorp/create

can you please let me know why i am getting this issue and due this i can’t use helm_release in terraform?

thanks

2

Hi @ukggupta, do you have some kind of invalid create statement in your code - like, e.g.

provider "create" {}
3

If you have multiple modules in your configuration then it might help to use the terraform providers command to see which of the modules is the one depending on hashicorp/create, in order to have less to search.

@tbugfinder is right that this is probably caused by a typo that Terraform is misinterpreting. An incorrect provider block is one possibility, and another would be a resource block with an incorrect resource type name that happens to have a create_ prefix:

resource "create_something" "example" {
  # ...
}

Terraform will, by default, assume that a resource type whose name starts with create_ belongs to a provider called hashicorp/create.

4

Hi All,

Sorry its typo and i have corrected myself. thanks