Bug #17815: Group API compatibility broken as it now always expects "properties" - Rudder - Issue Tracker

Actions

Copy link

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.

Status:

Released

Priority:

N/A

Assignee:

Vincent MEMBRÉ

Category:

API

Target version:

6.1.1

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Priority:

Name check:

To do

Fix check:

Checked

Regression:

Description

It should probably not be required, as it breaks compatibility for no good reason.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Alexis Mousset almost 4 years ago

Subject changed from Group API compatibility broken as it now always expectes "properties" to Group API compatibility broken as it now always expects "properties"

Actions

Copy link

Updated by François ARMAND almost 4 years ago

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.

Actions

Copy link