Missing data in quota REST API response

[nsc-jens]

dCache 10.2.11
Java 17

I think the REST API for quota has a bug. If I run a request for a project with quota > 0 I get:

curl -X GET "https://view.swestore.se:3880/api/v1/quota/group/7737" -H "accept: application/json"

[
{
"id": 7737,
"type": "GROUP",
"replica": 1214870414994,
"replicaLimit": 214748364800
}
]

This is as expected. But I set the quota to "0" I get an unexpected result:

[
{
"id": 8401,
"type": "GROUP",
"replica": 114046292506
}
]

It does report the usage but it doesn't report the quota size of zero. Perhaps a mixup between "NONE" and 0 somewhere?

We can mitigate this by setting the quota to "1" instead. We use it to implement a "read-delete-only" state for a project which is being decommissioned.

Additionally, a quota request for a project with no quota set reports:

{
"detail": "No such quota exists",
"title": "Not Found",
"status": "404"
}

which I guess is technically correct but could also have been reported as somethings like this without a tough 404 error:

[
{
"id": 8402,
"type": "GROUP",
}
]

But I have no strong opinions about this.

/jens

[DmitryLitvintsev]

Jens,

Json issue addressed, let's see what other dCache developers think about it (somebody put these conditions for some reason after all)

At this point I am reluctant to change behavior on attempt to get non existing quota.

My thinking is that all exising UIDs and GIDs need to be added to quota (w/o quota limits). So querying for UID/GID always return result unless UID/GID does not exist where 404 would be valid. It has benefit of easy monitoring of space used by users and groups.