Error while installing jfrog/mission-control v1.0.0: checksum list has no SHA-256 hash

[pokatov]

Describe the bug When trying to install jfrog/mission-control provider after executing terraform init command I get the following error:

Error: Failed to install provider
Error while installing jfrog/mission-control v1.0.1: checksum list has no SHA-256 hash for
"https://github.com/jfrog/terraform-provider-mission-control/releases/download/v1.0.1/terraform-provider-mission-control_1.0.1_darwin_arm64.zip"

I am using Terraform version 1.6.6 and the bug can be reproduced by executing terraform init command with the following Terraform configuration block:

terraform {
  required_providers {
    mission-control = {
      source  = "jfrog/mission-control"
      version = "1.0.1"
    }
  }
}

This happens for all three currently available versions - v1.0.0, v1.0.1, and v1.0.2. Artifactory version is 7.88.0.

Requirements for and issue

• [x] A description of the bug
• [x] A fully functioning terraform snippet that can be copy&pasted (no outside files or ENV vars unless that's part of the issue). If this is not supplied, this issue will likely be closed without any effort expended.
• [x] Your version of artifactory (you can curl it at $host/artifactory/api/system/version
• [x] Your version of terraform
• [x] Your version of terraform provider

Expected behavior A clear and concise description of what you expected to happen.

Additional context Add any other context about the problem here.

[pokatov]

Looks like similar issue was reported for jfrog/platform provider in https://github.com/jfrog/terraform-provider-platform/issues/111.

[alexhung]

@pokatov We recently switched to the Terraform Registry Org beta program and I suspect it may be the issue. 1.0.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.

[alexhung]

@pokatov HashiCorp is aware of this issue. They've manually fixed the issue for Artifactory provider and will be working on the same for this provider.

They have also identified the issue on their side and are working on a fix.

[alexhung]

HashiCorp has resolved the issue with this release. I've verified I can install 1.0.2 now.