rohityadavcloud commented on issue #109: URL: https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2058519817
@CodeBleu @Ye-Min-Tun @kiranchavala after some help from the Terraform registry support, I got the release removed and republished the artefacts again. With `Terraform v1.8.0` I was able to make init the provider with no errors: ``` > terraform init Initializing the backend... Initializing provider plugins... - Finding cloudstack/cloudstack versions matching "0.5.0"... - Installing cloudstack/cloudstack v0.5.0... - Installed cloudstack/cloudstack v0.5.0 (self-signed, key ID 484248210EE3D884) Partner and community providers are signed by their developers. If you'd like to know more about provider signing, you can read about it here: https://www.terraform.io/docs/cli/plugins/signing.html Terraform has created a lock file .terraform.lock.hcl to record the provider selections it made above. Include this file in your version control repository so that Terraform can guarantee to make the same selections by default when you run "terraform init" in the future. Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary. ``` Closing on this remark, please test if you still face any issues kindly reopen the issue. -- 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
