rohityadavcloud commented on issue #109: URL: https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2067725174
> > New provider version may need a whole new community release process. I think Tofu should fix the issue on their end as Terraform users aren’t affected. > > Is that an accurate statement? I thought you had to open ticket with Terraform Registry? Maybe they had to change their back end commit as well, so that it would pick up your changes to provider that was still using same version. To be clear, this is the CloudStack Terraform provider version, that needs to have a new RC put for vote and only then we can publish a new git tag. The issue we had was that our release manager published a git tag and deleted it, and later when it was created again Terraform registry failed to pick the new artefacts (here the version was still v0.5.0 but the publish/republish messed up the registry checksums/sha, which is supposedly immutable). To fix this the Terraform registry support first deleted the release at their end, and we had to delete/republish the tag+artifacts again using goreleaser. > The issue is not with new versions, the issue is when you update the release artifacts and SHAs in the repo, but do not change the version. I suppose the same thing has happened with Tofu, they need to delete old checksum/sha for their registry to re-registry the new tag+artifacts? > I can see it from both sides. Would be nice for both registries to just work with changing files, but not versions. Agree - registries should treat Github as source of truth, or at least some tools for valid authors/admins to delete/republish the same versions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
