Closed activalexsimon closed 1 month ago
We are also observing this issue.
@activalexsimon @adoraisa We recently switched to the Terraform Registry Org beta program and I suspect it may be the issue. 11.2.0 is the first version to be published after migrating to the beta program. Nothing on our side with regards to the packaging or signing of the provider has changed.
Looks like TF registry has not updated their copy of the checksum file due to file name parsing issue on their side.
Thanks for the feedback @alexhung!
Do you know when it will be resolved? Indeed, it seems like it is missing from https://releases.hashicorp.com/ (there is no terraform-provider-artifactory).
@kamilsimek-ecb I've opened support ticket with HashiCorp but I don't have any ETA.
The latest (not installable) version 11.2.0 is listed on the registry: https://registry.terraform.io/providers/jfrog/artifactory/11.2.0
@kamilsimek-ecb Commented too soon!
HashiCorp has resolved the issue with this release. I've verified I can install 11.2.0 now.
They have also identified the issue on their side and are working on a fix.
@alexhung thank you! Confirming on my end that I also can install 11.2.0.
Appreciate it!
Describe the bug I am seeing an error when trying to download the latest version of the provider due to SHA-256.
Local
CI
I am seeing this within out CI platforms and also on my local. Pinning the version back down to
v11.1.0
seems to resolve the issue and I am able to init just fine.Requirements for and issue
curl
it at$host/artifactory/api/system/version
Expected behavior I expect this providers version to also be working like v11.1.0 is.
Additional context This is for a different provider, but looks like a similar error.