Actions
Bug #25557
closedBug #25428: Update directive variable check constraints on existing values
Spaces as a default value provided by node properties are now refused
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
Not sure if it's the parent correction that lead to that problem (but likely), but now, in the case where:
- we have a mandatory string parameter, say udp_open_ports
(in firewall technique),
- the parameter is given in directive with ${node.properties[udp_open_ports] | default=" "}
- the node doesn't have the property defined,
Then we get the following error:
⇨ Cannot build target configuration node; cause was: Error while computing Node Configuration for nodes: ; cause was: Unexpected: Accumulated: Unexpected: Error with parameters expansion for node 'xxxxxx' (xxxxxx); cause was: Unexpected: Inconsistency: Error for policy for directive 'Firewall' [xxxxx] in rule 'Firewall' [xxxxx]: a non optional value is missing for parameter 'udp_open_ports' [param ID: 3021FC4F-DA33-4D84-8991-C42EBAB2335F] ;
Updated by François ARMAND 3 months ago
- 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/5906
Updated by Anonymous 2 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|67b2d367e7c48bb07c7f91a90affec8ad39a70ac.
Updated by Vincent MEMBRÉ about 1 month ago
- Status changed from Pending release to Released
Actions