Can't install versions after 1.18.0 about terraform-provider-minio HOT 16 CLOSED

v1.20.0 published! 🎉

from terraform-provider-minio.

Thanks for publishing a new release 👍
I can confirm that 1.20 is working fine.
Switching to a new repo/namespace in the future would be nice

from terraform-provider-minio.

Thank you @felladrin
I'll stick to 1.18.0 for now as a temporary workaround

from terraform-provider-minio.

We're finding the same issue but sticking with v1.18.0 has worked as a workaround.

from terraform-provider-minio.

If I may add my two cents, wouldn't it be easier to create a new gpg key and publish under the new repo name as well as the old repo for the first few patches/minors and eventually transition into just using the org one?

I'm no where near an expert and don't know if there are licensing fees and such but it seems like an idea.

Tl;dr;

Support both. publish for a bit (new + old) providers.

Deprecate the old provider and encourage people to transition to the new provider

Ending support/features/security updates at a set time for the old provider.

from terraform-provider-minio.

Indeed! Forking/mirroring might happen later, considering we still have that other intricate issue to solve.
In all cases, the original repo has to be back in place for the current provider to get back working.
But one issue at a time🤞

from terraform-provider-minio.

Yeah, working for us as well. Thanks @felladrin

from terraform-provider-minio.

You're right about the assets. I didn't catch them on the release page, sorry about that 😅
Still, install fails so there must be another reason

from terraform-provider-minio.

Same with me, using terraform 1.6.2

from terraform-provider-minio.

Published v1.19.0, including #520, but the shasums_url continue pointing to the previous repo.
We'll contact HashiCorp support to check what can be done. (Databricks has been through the same process)

from terraform-provider-minio.

Just to let you know that we're currently waiting for HashiCorp's support response on this.

from terraform-provider-minio.

Alright, everyone, we got a detailed response from one of the engineers from the Terraform Registry team, and, in summary, there's no way to change the provider in the Registry (aminueza/minio) for it to use the repository under our new organization.

Considering the situation, and also all the users that rely on this provider, here's what's going to happen next:
We'll move the repository back under aminueza's GitHub account, update the GPG key and literal URLs in the code, and finally publish v1.20.0 in the registry, which won't suffer from the Failed to install provider issue anymore.

Extra info: We won't dissolve the github.com/terraform-provider-minio organization because it will be redirecting the traffic to aminueza's repo and also because it might be useful for forks/sibling repos later. The advantage of having an organization is that the maintainers have more autonomy over the repositories.

from terraform-provider-minio.

Thanks for letting us know!
Will double-check the release workflow.

from terraform-provider-minio.

🤔 I see the shasum file is available at https://github.com/terraform-provider-minio/terraform-provider-minio/releases/tag/v1.18.3, and the shasum for terraform-provider-minio_1.18.3_linux_amd64.zip is there:

The published files in these release match the number of the files released in the previous one (v1.18.0).

from terraform-provider-minio.

Indeed.
I can't investigate deeper now, but I will do it soon.
Please keep me posted if you find out anything new about this issue.

[I doubt it, but this could be related to the repository address, which was changed recently.]

from terraform-provider-minio.

💡 I think the issue is really about the repository address. I checked the response of these two URLs:

• https://registry.terraform.io/v1/providers/aminueza/minio/1.18.0/download/linux/amd64 (when it was on the previous repo)
• https://registry.terraform.io/v1/providers/aminueza/minio/1.18.3/download/linux/amd64 (released from the current repository)

And the shasums URL hasn't been updated.

Previous	Current

The sad thing is that there's no option in Terraform Registry provider settings to change the repository ULR of a released provider.

from terraform-provider-minio.