Bug #17815
closed
Group API compatibility broken as it now always expects "properties"
Added by Alexis Mousset almost 4 years ago.
Updated almost 4 years ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Description
It should probably not be required, as it breaks compatibility for no good reason.
- Subject changed from Group API compatibility broken as it now always expectes "properties" to Group API compatibility broken as it now always expects "properties"
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 52
The API should be compatible, it's a bug if not so - API must not change if possible, and it's totally legit to create group without properties. But given the error message, it is not clear if the problem is not in the way we unserialise group query.
Setting to major as it's regression/incompatibility problem.
- Status changed from New to In progress
- Assignee set to François ARMAND
- Related to Bug #17814: Rudder (6.1) API missing documentation added
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/3097
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.1 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by