rhtyd commented on issue #22:
URL: https://github.com/apache/cloudstack-go/issues/22#issuecomment-973882596
okay, well the intension of the SDK is to not necessarily support all the
APIs as APIs may keep growing - it's meant to be driven by users/usage.
--
This is an automated message fr
Pearl1594 commented on issue #22:
URL: https://github.com/apache/cloudstack-go/issues/22#issuecomment-973873511
@rhtyd updating listAPIs.json doesn't support all the APIs we need to add
them to the layout file as well. So, they may still not be supported
--
This is an automated message f
rhtyd commented on issue #22:
URL: https://github.com/apache/cloudstack-go/issues/22#issuecomment-973868840
@davidjumani check latest main now, confirm close the issue if this is fixed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
rhtyd merged pull request #16:
URL: https://github.com/apache/cloudstack-go/pull/16
--
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..
rhtyd commented on pull request #16:
URL: https://github.com/apache/cloudstack-go/pull/16#issuecomment-973865861
i'll merge this but then update the listapis again to check
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
davidjumani commented on issue #22:
URL: https://github.com/apache/cloudstack-go/issues/22#issuecomment-973865172
It's fine if some obscure APIs don't get in asap but certain new / common
apis should go in :
```
destroyVolume
listVolumesMetrics
recoverVolume
addAnnota
davidjumani opened a new issue #22:
URL: https://github.com/apache/cloudstack-go/issues/22
Here's a list of the APIs not yet added to the SDK
```
acquirePodIpAddress
addAnnotation
addCiscoAsa1000vResource
addCiscoVnmcResource
addExternalFirewall
addExternalLoadBalanc
hrak commented on issue #16:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/16#issuecomment-973846197
If there is no way to transform the source_nat_ip_id into the actual IP
address, then i guess there is no way around the additional IP for now. Thanks
for your quick