Filter on parameter listing empty objects when filtered parameter doesn't exists

[sureshanaparti]

Apache CloudStack 🐵 CloudMonkey 6.5.0

(localcloud) 🐱 > list usagerecords startdate=2025-10-07 enddate=2025-10-10 type=6 usageid=2c218702-abff-46e8-bc8a-3e12fffa2188 filter=count
{
  "count": 319,
  "usagerecord": [
    {},
    {},
    {},
    {},
    {},
    {},
    {},
...
    {},
    {},
    {}
  ]
}

Expected:

(localcloud) 🐱 > list usagerecords startdate=2025-10-07 enddate=2025-10-10 type=6 usageid=2c218702-abff-46e8-bc8a-3e12fffa2188 filter=count
{
  "count": 319
}

[dheeraj12347]

Hi, I was looking into CloudMonkey issues while exploring the CLI codebase and came across this one.

It seems that when filter=count is applied, the filtering logic still iterates over the result objects and prints empty {} entries instead of returning only the filtered field. I’d like to investigate the filtering/output handling to ensure that when the filtered parameter doesn’t exist in the objects, the CLI only returns the filtered value (e.g., { "count": 319 }).

If no one is currently working on this, I’d be happy to take a look and propose a fix.

[dheeraj12347]

Hi, I’ve submitted a fix in PR #208.

This resolves the issue where empty objects were shown when using filter=count.

Would appreciate feedback!