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

2024-03-14 Thread via GitHub
vishesh92 commented on issue #32: URL: https://github.com/apache/cloudstack-terraform-provider/issues/32#issuecomment-1996877510 @kohrar I did a few tests. When I associate an ip_address with a network id, associated network id is set in response. But when I associate it with a vpc id, ass

Re: [PR] Restore methods with optional params for 4.19 compatability [cloudstack-go]

2024-03-14 Thread via GitHub
weizhouapache commented on PR #80: URL: https://github.com/apache/cloudstack-go/pull/80#issuecomment-1997179814 thanks @vishesh92 it looks terraform will not work https://github.com/apache/cloudstack-terraform-provider/blob/d524e07e497b44caf3252fe9ffeefbc6bd138570/cloudstack/r

Re: [PR] Restore methods with optional params for 4.19 compatability [cloudstack-go]

2024-03-14 Thread via GitHub
shwstppr merged PR #80: URL: https://github.com/apache/cloudstack-go/pull/80 -- 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.

Re: [PR] Fail when both network_id & vpc_id are set in ipaddress [cloudstack-terraform-provider]

2024-03-14 Thread via GitHub
vishesh92 merged PR #99: URL: https://github.com/apache/cloudstack-terraform-provider/pull/99 -- 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-unsubs

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

2024-03-14 Thread via GitHub
vishesh92 closed issue #32: network_id remains empty after creating IP address resource URL: https://github.com/apache/cloudstack-terraform-provider/issues/32 -- 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

Re: [VOTE] next version 20 instead of 4.20

2024-03-14 Thread João Jandre Paraquetti
Hi all, I know that this discussion has cooled off, but I think it's still extremely relevant for the future of ACS. 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) for

Re: [VOTE] next version 20 instead of 4.20

2024-03-14 Thread Rohit Yadav
Joao, Could you start a separate [DISCUSS] thread, this is because your proposal is important in the context of future of ACS releases, but different from what this voting thread is about. There are no bylaw(s) on how many releases should be done in a year or have them done in a certain way; w