Actions
Bug #20871
closed
Some api response have an id field but should'nt have one
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
id field in api response represents the identifier of resource that is asked by the request. In case of a request that ask multiple values (ie lists), or data that have no id (ie plugin config, last cve check, directive tree) we should not send an id
This is mostly visible in CVE plugin (which also send their id), but also with directive tree api which set "tree" as an id
This was introduced since a new way to send Json response in #19869 force to have a value as id for json response ... but it should not be the case and the id should be optionnal
Updated by 
Updated by
Actions