Project

General

Profile

Actions

Bug #25557

open

Bug #25428: Update directive variable check constraints on existing values

Spaces as a default value provided by node properties are now refused

Added by François ARMAND about 1 month ago. Updated 27 days ago.

Status:
Pending release
Priority:
N/A
Category:
Web - Config management
Target version:
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] ; 

Subtasks 2 (2 open0 closed)

Bug #25569: List directive API does not return the correct valueNewActions
Bug #25579: System variable can be empty early on the generation processPending releaseVincent MEMBRÉActions
Actions

Also available in: Atom PDF