Re: [I] v2.15.0 breaking change regarding displayText handling for CreateNetwork [cloudstack-go]

2024-03-15 Thread via GitHub
shwstppr closed issue #70: v2.15.0 breaking change regarding displayText handling for CreateNetwork URL: https://github.com/apache/cloudstack-go/issues/70 -- 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 g

Re: [I] v2.15.0 breaking change regarding displayText handling for CreateNetwork [cloudstack-go]

2024-03-15 Thread via GitHub
shwstppr commented on issue #70: URL: https://github.com/apache/cloudstack-go/issues/70#issuecomment-1999201665 Closing this based on recent changes and provision for forcing params to be required in #79 @hrak please reopen if we need further work. -- This is an automated message from

[DISCUSS] Define a release schedule for the project

2024-03-15 Thread João Jandre Paraquetti
Hi all, I had posted this message on another thread, but following Rohit's advice I've decided to create a new one for it. That being said, I have another proposal for the versioning scheme. Instead of dropping the "X" on our X.Y.Z.N, we can set a fixed schedule (that can be further discussed

Re: [PROPOSE] RM for Cloudstack Terraform Provider

2024-03-15 Thread Rohit Yadav
All, Kiran is release manager for the next Terraform provider release (v0.5.0) but isn't a committer to have commit privileges to the upstream repo (something PMC can help into?). To assist him, I've created a pre-RC (alpha) build for testing purposes and we encourage users to test and report

Re: [PR] Update SDKs [cloudstack-terraform-provider]

2024-03-15 Thread via GitHub
fabiomatavelli commented on PR #71: URL: https://github.com/apache/cloudstack-terraform-provider/pull/71#issuecomment-2000341643 @CodeBleu I was looking into migrating directly to the terraform plugin framework and it will require a huge effort for that. It will be not as simple as migrati

Re: [PR] Update SDKs [cloudstack-terraform-provider]

2024-03-15 Thread via GitHub
fabiomatavelli commented on PR #71: URL: https://github.com/apache/cloudstack-terraform-provider/pull/71#issuecomment-2000343098 @vishesh92 @rohityadavcloud I've added another matrix to the acceptance test so multiple versions of terraform can be tested. -- This is an automated message f

Re: [I] network_id remains empty after creating IP address resource [cloudstack-terraform-provider]

2024-03-15 Thread via GitHub
kohrar commented on issue #32: URL: https://github.com/apache/cloudstack-terraform-provider/issues/32#issuecomment-2000422662 @vishesh92 I don't think that's a valid solution. There are cases where I need to specify both VPC and network ID. For instance, when I need to assign a public IP a

Re: [I] network_id remains empty after creating IP address resource [cloudstack-terraform-provider]

2024-03-15 Thread via GitHub
kohrar commented on issue #32: URL: https://github.com/apache/cloudstack-terraform-provider/issues/32#issuecomment-2000433572 Perhaps I'm misunderstanding how public IPs are assigned to VPC and networks. I don't actually need to specify the network if I'm using VPCs. The above exampl

Re: [PR] Update SDKs [cloudstack-terraform-provider]

2024-03-15 Thread via GitHub
CodeBleu commented on PR #71: URL: https://github.com/apache/cloudstack-terraform-provider/pull/71#issuecomment-2000607396 > @CodeBleu I was looking into migrating directly to the terraform plugin framework and it will require a huge effort for that. It will be not as simple as migrating f