CodeBleu commented on issue #109: URL: https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2067675036
> 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. 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 can see it from both sides. Would be nice for both registries to just work with changing files, but not versions. At the same time it does make sense that if something changed in the release artifacts that it would make sense to bump the patch version. -- 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
