All, Update - looks like there was a caching/delay issue, after republishing the provider the issue is no longer seen now (as tested with Terraform v1.8.0 CLI) and a workaround release may not be necessary now.
Issue reference: https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2058519817 The only note for future release manager is to avoid publishing the artifacts before voting is closed, or to delete an already published release. Regards. ________________________________ From: Rohit Yadav <rohit.ya...@shapeblue.com> Sent: Tuesday, April 16, 2024 13:15 To: dev <dev@cloudstack.apache.org> Subject: Re: [DISCUSS] New terraform git tag for registry workaround All, I got the following from TF support: Hello there, provider versions are immutable in the registry. Therefore, when you deleted and recreated the version in Github, the hash has changed, and the registry will refuse to serve it. Your option now it either to delete the version in the registry (which we can help you do), or publish a new version. I tried to get the release deleted from the registry, and republished the releases artifacts using goreleaser but still same issue. I think the only thing to document is that we must never delete/republish an artifact on the release repo: http://github.com/cloudstack/terraform-provider-cloudstack We cannot use the apache one as: (1) the registry needs the repo to be named as terraform-provider-<name> and (2) it would need access from asf infra to connect registry with the repo, and it would then need existing users to migrate from cloudstack/cloudstack provider namespace (as the plugin has history/registry even before being donated to the cloudstack project). Regards. ________________________________ From: Harikrishna Patnala <harikrishna.patn...@shapeblue.com> Sent: Tuesday, April 16, 2024 11:54 To: dev <dev@cloudstack.apache.org> Subject: Re: [DISCUSS] New terraform git tag for registry workaround okay, given the situation your proposal seems right Rohit. Like Daan asked, if we can prevent this situation in future we need to document it also. Regards, Harikrishna ________________________________ From: Daan Hoogland <daan.hoogl...@gmail.com> Sent: Monday, April 15, 2024 4:50 PM To: dev <dev@cloudstack.apache.org> Subject: Re: [DISCUSS] New terraform git tag for registry workaround I think your proposals are ok as an ad-hoc solution to the current situation @Rohit Yadav . I wonder how we should deal with this in the future though. 1. As for the numbering, do we have a procedure to prevent this issue in the future? 2. The provider is part of apache and I think the link https://github.com/apache/terraform-provider-cloudstack should be validated. What exactly is the objection to this? On Mon, Apr 15, 2024 at 12:05 PM Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > > All, > > The recent Terraform provider release v0.5.0 has a problem with the Terraform > registry website. > https://github.com/apache/cloudstack-terraform-provider/issues/109 > > The registry support isn't able to provide a resolution now, their manual > resync button on the provider isn't fixing the issue. > > While I've documented the steps for manually installing and using the > provider. Most terraform/tofu users are used to consuming a provider from the > registry. > > If there are no objections, I propose that we just tag the current version as > v0.5.1 and push it on the registry for the purpose of publishing on the > registry website. We may need not do a formal vote for this as code wise > nothing has changed and we can make this tag to be a community release tag > solely done for the purpose of having a workaround on the registry website > https://registry.terraform.io/providers/cloudstack/cloudstack/latest which > gets published via > https://github.com/cloudstack/terraform-provider-cloudstack as the registry > also has a strict repo naming policy (due to which it can't use the repo > under Apache org). > > Thoughts? > > Regards. > > > -- Daan
