Actions
Bug #5982
closedIn API/rules include/exclude is ordered for target parameter
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In the rule API (update, creation), include and exclude are ordered for the target parameter, so that:
"targets": [ { "exclude": {"or": ["policyServer:root"] }, "include": {"or": ["group:foo"]} }]
Leads to error:
"errorDetails": "Could not create Rule 60214a59-8d07-4446-9db1-36feb5342f3f cause is: JObject(List(JField(exclude,JObject(List(JField(or,JArray(List(JString(policyServer:root))))))), JField(include,JObject(List(JField(or,JArray(List(JString(group:foo))))))))) is not a valid rule target."
But:
"targets": [ { "include": {"or": ["group:foo"]}, "exclude": {"or": ["policyServer:root"] } }]
Works fine. But JSON fields are not sorted.
Updated by François ARMAND about 10 years ago
- Status changed from New to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/717
Updated by François ARMAND about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 0ebfb747f4d65aeb112cc6607a2d69da3ebe7e6f.
Updated by Nicolas CHARLES about 10 years ago
Applied in changeset 4024dee1cce3d65cd9dcdc1cfc5a293fdd9f4e12.
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.9 to 2.10.10
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.10 and 2.11.7, which were these days.
- Announcement 2.10 2.11
- Changelog 2.10 2.11
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions