Actions
Enhancement #16251
openImprove message when using a wrong syntax for a node property in technique editor
Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Name check:
To do
Fix check:
To do
Regression:
Description
I tried to create a technique using a wrong syntax using the node properties:
${node.properties.key[subkey]} instead of ${node.properties[key][subkey]}
Current error message is :
Could not update ncf technique <- Error when translating parameter '${node.properties.[key][subkey]}' of technique of method BundleName(command_execution) of technique test <- Error when parsing value "${node.properties.[key][subkey]}", error message is: end of input expected
It could explain that it parsed a node property and what is the correct syntax
Updated by Vincent MEMBRÉ about 5 years ago
- Related to Bug #15048: Error message in technique editor when using wrong syntax for node properties is REALLY not clear enough added
Updated by Alexis Mousset about 5 years ago
- Subject changed from Improve message when using a worng syntax for a node property in technique editor to Improve message when using a wrong syntax for a node property in technique editor
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.15 to 5.0.16
Updated by Alexis Mousset almost 5 years ago
- Target version changed from 5.0.16 to 5.0.17
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by François ARMAND over 4 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 29
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.18 to 5.0.19
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.19 to 5.0.20
- Priority changed from 29 to 28
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.20 to 797
- Priority changed from 28 to 27
Updated by Benoît PECCATTE over 3 years ago
- Target version changed from 797 to 6.1.14
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by François ARMAND almost 3 years ago
- Tracker changed from Bug to Enhancement
- Severity deleted (
Minor - inconvenience | misleading | easy workaround) - Priority deleted (
27)
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.19 to 6.1.20
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.20 to 6.1.21
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
Updated by Alexis Mousset almost 2 years ago
- Target version changed from old 6.1 issues to relocate to 7.2.5
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.2.5 to 7.2.6
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.6 to 7.2.7
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.7 to 7.2.8
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.8 to 7.2.9
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.9 to 7.2.10
Updated by Alexis Mousset over 1 year ago
- Target version changed from 7.2.10 to 7.2.11
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.11 to 1046
Updated by Alexis Mousset about 1 year ago
- Target version changed from 1046 to Ideas (not version specific)
Actions