filter is ignored on e.g. deploy virtual machine about cloudstack-cloudmonkey HOT 9 OPEN

@DaanHoogland filters are used only for list/get API or any sync API - https://github.com/apache/cloudstack-cloudmonkey/wiki/Usage#output

from cloudstack-cloudmonkey.

I know, and that could be im[proved, couldn´t it, @rohityadavcloud ?

from cloudstack-cloudmonkey.

@DaanHoogland can you suggest your use-case? we can of course keep it as feature/improvement request.

workaround - Maybe you can grab the VM's uuid and call the list API subsequently to filter stuff (I'm not sure if the deploy vm response sends the entire list VM response as expected, incl things like details etc).

from cloudstack-cloudmonkey.

I am doing a test in which I want to make sure that not all of the deploy VM commands succeed and want to get only the name and id of those VMs that do succeed. At the same time I want to see the error output of those that fail without feeding those into a grep command.
I think the second command syntax I gave in the description would be the best intuitive way to deal with this, but the first one would be the most consistent with the list APIs.

from cloudstack-cloudmonkey.

Hi guys, +1 on the improvement request

from cloudstack-cloudmonkey.

@DaanHoogland I'm working on the milestone for 6.3.0 and I'm wondering should we add this improvement. Do you have any idea how much effort it is going to take, are you willing to work on it?

from cloudstack-cloudmonkey.

@DaanHoogland to look for exact estimate and come back

from cloudstack-cloudmonkey.

So I had a look, and this will require the filter() method from the output module to be converted into a small module and to add knowledge of the possible structures of the response to be filtered. This might have to be extendible if more possible response structures come up. but initially it just needs to distinct list-responses from the requested deployVirtualMachine response. a middle sized project probably.

from cloudstack-cloudmonkey.

Guys, I will prefer that filter is supported and used only for list/get APIs as originally intended and documented - https://github.com/apache/cloudstack-cloudmonkey/wiki/Usage#output

CloudStack has 100s of async APIs, to support all of those APIs by a simple CLI would be too much of a task both in terms of implementation and testing. Perhaps filter autocompletion can be made such that it's not available for any async APIs to restrict that. cc @borisstoyanov @nvazquez

from cloudstack-cloudmonkey.