New plugin publish error

Terraform Providers Plugin Development
1

Hi.

I am trying to publish a new provider but I keep getting this error.

Error loading provider: Error: No provider versions found

After the first publish I see it part of the Terraform Registry as I can select it when I hit publish, but I stil get the same error.

I want to note that the webhook has been created and that I followed the guide here.

I don’t have (or know of) any other place to see details about the error that is preventing publishing the provider/module.

Any help would be greatly appreciated.

2

i’m in the same boat, this is really an unhelpful error message. Did you resolve it?

3

@cuzzea Has this been resolved? I see that I can now use this provider on darwin_arm64.

If you have any further questions, please let me know.

$ terraform init
Initializing the backend...
Initializing provider plugins...
- Finding envtrack/envtrack versions matching "1.0.2"...
- Installing envtrack/envtrack v1.0.2...
- Installed envtrack/envtrack v1.0.2 (self-signed, key ID D3D4A4254A6B6C3F)
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
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

-Baraa, Terraform Developer Experience

4

@hansbogert: if you are still looking for assistance with this, please let me know. The name, version, and source repository of the provider will be helpful.

-Baraa, Terraform Developer Experience

5

This is solved through email/service desk with the registry team.

The error messaging is just really poor in the web UI. The cause was that some official providers have some magic somewhere in the pipeline dealing with markdown in the website/ folder of the repo.

This magic is not triggered when cloning the repoe and trying to do a barebones release with the source code as is.

I removed the /website folder (among a lot of other hashicorp specific CI stuff) and it started working. An hashicorp employee hinted towards the markdown rendering error which only employees could see in hashicorp logging.

1 Like