Actions
Bug #24993
open
Inconsistency : Directives consider empty strings are “undefined” while default replacement mechanisms don't
Status:
New
Priority:
N/A
Assignee:
-
Category:
-
Target version:
-
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
34
Name check:
To do
Fix check:
To do
Regression:
No
Description
When a node property value is set to the empty string,
- It is not overriden by a default value set in Rudder's global parameters
- It is not overriden by a
| default="something"in directive parameters
So, as far as replacement mechanisms are concerned, the empty string is not “undefined”.
However, directives using parameters that evaluate to "" cause the generation to fail with an “undefined parameter” message.
This behaviour is inconsistent.
Either "" should be overriden by the default mechanisms, or directives should accept an empty string as a valid parameter value.
Updated by Clark ANDRIANASOLO 5 months ago
- Blocked by Bug #24778: Groups tables needs pagination added
Updated by Michel BOUISSOU 5 months ago
- Subject changed from Iconsistency : Directives consider empty strings are “undefined” while default replacement mechanisms don't to Inconsistency : Directives consider empty strings are “undefined” while default replacement mechanisms don't
Actions