Actions
Bug #23380
closed
Rudderc silently accept unknown parameter constraints
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
The following technique is valid for the current rudderc:
---
id: min
name: NTP
version: "0.1"
params:
- id: d76ce2e5-d5b6-45cc-87e8-c11cca71d907
name: param1
default: bob
constraints:
does_not_exist: patapouf
items:
- id: d86ce2e5-d5b6-45cc-87e8-c11cca71d907
method: package_present
params:
name: "htop"
version: "2.3.4"
We should prohibit the user to define unknown constraints.
Updated by Félix DALLIDET 8 months ago
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
Updated by Félix DALLIDET 8 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/5025
Updated by Félix DALLIDET 8 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|aa66b5eb14ea723d3e1bc61728d3c43a22da1886.
Updated by Vincent MEMBRÉ 8 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.0.0~beta1 which was released today.
Actions