CodeBleu commented on issue #109: URL: https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2067717157
> > 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. > > AFAIK, the terraform registry have been updated. anyone (you/we/others) can create a pull request to fix the SHA values in tofu registry (https://github.com/opentofu/registry/blob/7e4023585a04613a12dd150cec45e114788db02b/providers/c/cloudstack/cloudstack.json as you mentioned) https://github.com/opentofu/registry/pulls this could be easiest way @weizhouapache As I mentioned [here](https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2067660251) in my previous experience, they have have recommended "going forward" to bump the version, but feel free to try and create a PR for them. I have personally asked them twice before and that is why I got the "going forward" statement from them. I have messaged them in their Slack channel with this issue and if they feel like doing it again or approving someone else's PR, then I say go for it, but I do not feel comfortable asking them again at this point. Also, it doesn't make sense to me that literally anyone can submit a PR change for a repo they don't maintain. So, even more reason for a maintainer of this repo to make a request to them. If there is some actual small changes with this provider that can benefit the community and do a minor patch version update to 0.5.1 then we all win! I'm not sure how soon this issue is going to go away, especially if provider owners are changing their release files without actually bumping the version, but I would assume that now the issue is known here, that when the future releases are published, that the proper files will just be part of CI/CD or release script so that things will just work going forward. -- 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
