Project

General

Profile

Actions
Copy link

Bug #27384

open

Missleading format for parameter category in API

Added by Elaad FURREEDAN about 1 month ago. Updated 9 days ago.

Status:
Pending technical review
Priority:
1 (highest)
Assignee:
Elaad FURREEDAN
Category:
API
Target version:
8.2.9
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
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

Related issues 1 (1 open — 0 closed)

Related to Rudder - Bug #27383: categoryId field is missing from API response documentationNewElaad FURREEDANActions
Actions
Copy link
 #1

Updated by Elaad FURREEDAN about 1 month ago

  • Priority changed from N/A to To review
Actions
Copy link
 #3

Updated by François ARMAND 24 days 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.

Actions
Copy link
 #4

Updated by François ARMAND 24 days ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by Nicolas CHARLES 24 days ago

  • Related to Bug #27383: categoryId field is missing from API response documentation added
Actions
Copy link
 #6

Updated by Elaad FURREEDAN 10 days ago

  • Status changed from New to In progress
Actions
Copy link
 #7

Updated by Elaad FURREEDAN 9 days ago

  • Status changed from In progress to Pending technical review
  • Pull Request set to https://github.com/Normation/rudder/pull/6572
Actions
Copy link

Also available in: Atom PDF