[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. While I've documented the steps for manually installing and using the provider. Most terraform/tofu users are used to consuming a provider from the registry. If there are no objections, I propose that we just tag the current version as v0.5.1 and push it on the registry for the purpose of publishing on the registry website. We may need not do a formal vote for this as code wise nothing has changed and we can make this tag to be a community release tag solely done for the purpose of having a workaround on the registry website https://registry.terraform.io/providers/cloudstack/cloudstack/latest which gets published via https://github.com/cloudstack/terraform-provider-cloudstack as the registry also has a strict repo naming policy (due to which it can't use the repo under Apache org). Thoughts? Regards.
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://github.com/apache/terraform-provider-cloudstack should be validated. What exactly is the objection to this? On Mon, Apr 15, 2024 at 12:05 PM Rohit Yadav wrote: > > 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. > > While I've documented the steps for manually installing and using the > provider. Most terraform/tofu users are used to consuming a provider from the > registry. > > If there are no objections, I propose that we just tag the current version as > v0.5.1 and push it on the registry for the purpose of publishing on the > registry website. We may need not do a formal vote for this as code wise > nothing has changed and we can make this tag to be a community release tag > solely done for the purpose of having a workaround on the registry website > https://registry.terraform.io/providers/cloudstack/cloudstack/latest which > gets published via > https://github.com/cloudstack/terraform-provider-cloudstack as the registry > also has a strict repo naming policy (due to which it can't use the repo > under Apache org). > > Thoughts? > > Regards. > > > -- Daan
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 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
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] 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://github.com/apache/terraform-provider-cloudstack should be validated. What exactly is the objection to this? On Mon, Apr 15, 2024 at 12:05 PM Rohit Yadav wrote: > > 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. > > While I've documented the steps for manually installing and using the > provider. Most terraform/tofu users are used to consuming a provider from the > registry. > > If there are no objections, I propose that we just tag the current version as > v0.5.1 and push it on the registry for the purpose of publishing on the > registry website. We may need not do a formal vote for this as code wise > nothing has changed and we can make this tag to be a community release tag > solely done for the purpose of having a workaround on the registry website > https://registry.terraform.io/providers/cloudstack/cloudstack/latest which > gets published via > https://github.com/cloudstack/terraform-provider-cloudstack as the registry > also has a strict repo naming policy (due to which it can't use the repo > under Apache org). > > Thoughts? > > Regards. > > > -- Daan
