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 Sent: Monday, April 15, 2024 4:50 PM To: dev Subject: Re: [DISCUSS] N

Re: [PR] [StepSecurity] ci: Harden GitHub Actions [cloudstack-go]

DaanHoogland commented on PR #81: URL: https://github.com/apache/cloudstack-go/pull/81#issuecomment-2056612835 @rohityadavcloud as the build passes can we merge this (cc @jbampton )? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

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:

[DISCUSS] New terraform git tag for registry workaround

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