Actions
Bug #20871
closed
Some api response have an id field but should'nt have one
Bug #20871:
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 Vincent MEMBRÉ almost 4 years ago
- Status changed from New to In progress
Updated by Vincent MEMBRÉ almost 4 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/4200
Updated by Vincent MEMBRÉ almost 4 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder|e343b36d4cacc642f6f6c997c7810f56ea2c4692.
Updated by François ARMAND almost 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.2 and 7.1.0~rc1 which were released today.
Actions