[
https://issues.apache.org/jira/browse/CLOUDSTACK-8133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682086#comment-14682086
]
ASF GitHub Bot commented on CLOUDSTACK-8133:
--------------------------------------------
GitHub user borisroman opened a pull request:
https://github.com/apache/cloudstack/pull/679
Added Virtualmachine count and ID's to listSecurityGroups response
See issue CLOUDSTACK-8133 for more information.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/borisroman/cloudstack CLOUDSTACK-8133
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/679.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #679
----
commit f4449b62d93e56d9f62fac06922b12381a51b8e4
Author: Boris Schrijver <[email protected]>
Date: 2015-08-11T17:01:38Z
CLOUDSTACK-8133 Added Virtualmachine count and ID's to listSecurityGroups
response.
See issue CLOUDSTACK-8133 for more information.
----
> Add instance count to listSecurityGroups API call.
> --------------------------------------------------
>
> Key: CLOUDSTACK-8133
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8133
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Reporter: Kevin Dierkx
> Assignee: Boris Schrijver
> Priority: Minor
> Fix For: 4.6.0
>
>
> Currently the listSecurityGroups call doesn't return an instance count of
> some sort. There is no way of knowing without polling all VMs if the security
> group is empty and will result in an exception on removal.
> It would be awesome if this information could be provided with the above call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
