Actions
Bug #27384
closedMissleading format for parameter category in API
Bug #27384:
Missleading format for parameter category in API
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
When we POST (update) and PUT (create) a rule from the API, we can specify category by using his ID.
To specify ID we have to use in the JSON category, in the response the parameter is categoryId
Updated by Elaad FURREEDAN 7 months ago
- Priority changed from N/A to To review
Updated by François ARMAND 7 months ago
- Assignee set to Elaad FURREEDAN
- Priority changed from To review to 1 (highest)
I think we want categoryId every where.
Version is really 8.2 for support.
Updated by François ARMAND 7 months ago
- Description updated (diff)
Updated by Nicolas CHARLES 7 months ago
- Related to Bug #27383: categoryId field is missing from API response documentation added
Updated by Elaad FURREEDAN 7 months ago
- Status changed from New to In progress
Updated by Elaad FURREEDAN 7 months ago
- Status changed from In progress to Pending technical review
- Pull Request set to https://github.com/Normation/rudder/pull/6572
Updated by Clark ANDRIANASOLO 6 months ago
- Assignee changed from Elaad FURREEDAN to Clark ANDRIANASOLO
Updated by Clark ANDRIANASOLO 6 months ago
- Related to Enhancement #27531: Return categoryId in JSON groups API added
Updated by Anonymous 6 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|12ca550b2f3f73e1ab54507a61ecb1d822a5e23c.
Updated by Clark ANDRIANASOLO 6 months ago
- Subtask #27538 added
Updated by Vincent MEMBRÉ 6 months ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 6 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.9 and 8.3.4 which were released today.
Actions